On Tue, Oct 30, 2007 at 03:11:20PM +0100, Jarek Poplawski wrote:
> On Mon, Oct 29, 2007 at 01:41:47AM -0700, David Miller wrote:
> ...
> > Actually, this was caused by a real bug in the SKB_WITH_OVERHEAD macro
> > definition, which Herbert Xu quickly spotted and fixed.
> >
> > Which "I hope you've
On Mon, Oct 29, 2007 at 01:41:47AM -0700, David Miller wrote:
...
> Actually, this was caused by a real bug in the SKB_WITH_OVERHEAD macro
> definition, which Herbert Xu quickly spotted and fixed.
>
> Which "I hope you've found this by yourself by now".
>
...Btw, of course you have to be right,
On Mon, Oct 29, 2007 at 01:41:47AM -0700, David Miller wrote:
> From: Jarek Poplawski <[EMAIL PROTECTED]>
> Date: Mon, 29 Oct 2007 09:42:32 +0100
>
> > I hope you've found this by yourself by now, but:
> >
> > 1. These are warnings only - not oopses.
> > 2. It seems this patch you've found to be
From: Jarek Poplawski <[EMAIL PROTECTED]>
Date: Mon, 29 Oct 2007 09:42:32 +0100
> I hope you've found this by yourself by now, but:
>
> 1. These are warnings only - not oopses.
> 2. It seems this patch you've found to be responsible for this all
> slightly changes some limits, which is not necess
On 15-10-2007 17:39, Darko K. wrote:
> Hello,
>
> after recent upgrade to kernel 2.6.23 (from 2.6.20) I have started
> seeing kernel oops-es in networking code. The problem is 100%
> reproducible in my environment. I've seen two slightly different
> backtraces but both seem to be caused by the sam
Hello,
after recent upgrade to kernel 2.6.23 (from 2.6.20) I have started
seeing kernel oops-es in networking code. The problem is 100%
reproducible in my environment. I've seen two slightly different
backtraces but both seem to be caused by the same commit. Please
put me on Cc: on replies.
I've
