netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: David Miller <davem@davemloft.net>
Cc: darko.koruga@siol.net, netdev@vger.kernel.org
Subject: Re: Oops in 2.6.21-rc4, 2.6.23
Date: Mon, 29 Oct 2007 14:13:48 +0100	[thread overview]
Message-ID: <20071029131348.GA2999@ff.dom.local> (raw)
In-Reply-To: <20071029.014147.56411400.davem@davemloft.net>

On Mon, Oct 29, 2007 at 01:41:47AM -0700, David Miller wrote:
> From: Jarek Poplawski <jarkao2@o2.pl>
> 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 necessarily wrong; the
> > lucky thing is you can change these limits with sysctl or some
> > echos to /proc/sys/net/ipv4/tcp_mem, I presume. (Or more safely by
> > adding some memory.)
> 
> Actually, this was caused by a real bug in the SKB_WITH_OVERHEAD macro
> definition, which Herbert Xu quickly spotted and fixed.

But, since Darko has found this other patch matters for him too, maybe
there could be more than one cause to 'blame' for such differences
from 2.6.20 (maybe it's not all yet) - especially if it's all around
some limits.

> 
> Which "I hope you've found this by yourself by now".
> 

I think it's unfair! Darko got 2 weeks for thinking about this all...

Thanks,
Jarek P.

  reply	other threads:[~2007-10-29 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 15:39 Oops in 2.6.21-rc4, 2.6.23 Darko K.
2007-10-29  8:42 ` Jarek Poplawski
2007-10-29  8:41   ` David Miller
2007-10-29 13:13     ` Jarek Poplawski [this message]
2007-10-30 14:11     ` Jarek Poplawski
2007-10-31  8:39       ` Jarek Poplawski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071029131348.GA2999@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=darko.koruga@siol.net \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).