From: Stephen Hemminger <shemminger@osdl.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Boris B. Zhmurov" <bb@kernelpanic.ru>,
Phil Oester <kernel@linuxace.com>,
Mark Nipper <nipsy@bitgnome.net>,
"David S. Miller" <davem@davemloft.net>,
jesse.brandeburg@intel.com, jrlundgren@gmail.com, cat@zip.com.au,
djani22@dynamicweb.hu, yoseph.basri@gmail.com, mykleb@no.ibm.com,
olel@ans.pl, michal@feix.cz, chris@scorpion.nl,
netdev@vger.kernel.org, jesse.brandeburg@gmail.com,
Andi Kleen <ak@suse.de>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [TCP]: Fix truesize underflow
Date: Wed, 19 Apr 2006 09:53:48 -0700 [thread overview]
Message-ID: <20060419095348.0de93eaf@localhost.localdomain> (raw)
In-Reply-To: <20060418123204.GA3962@gondor.apana.org.au>
On Tue, 18 Apr 2006 22:32:04 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Hi Dave:
>
> You're absolutely right about there being a problem with the TSO packet
> trimming code. The cause of this lies in the tcp_fragment() function.
>
> When we allocate a fragment for a completely non-linear packet the
> truesize is calculated for a payload length of zero. This means that
> truesize could in fact be less than the real payload length.
>
> When that happens the TSO packet trimming can cause truesize to become
> negative. This in turn can cause sk_forward_alloc to be -n * PAGE_SIZE
> which would trigger the warning.
>
> I've copied the code you used in tso_fragment which should work here.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> Everyone who's having the sk_forward_alloc warning problem should give
> this patch a go to see if it cures things.
>
> Just in case this still doesn't fix it, could everyone please also verify
> whether disabling SMP has any effect on reproducing this?
>
> Thanks,
Please put this in the next -stable load...
next prev parent reply other threads:[~2006-04-19 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 12:32 [TCP]: Fix truesize underflow Herbert Xu
2006-04-18 16:29 ` Ingo Oeser
2006-04-18 20:19 ` David S. Miller
2006-04-18 20:22 ` David S. Miller
2006-04-18 23:27 ` Herbert Xu
2006-04-19 6:04 ` Boris B. Zhmurov
2006-04-19 6:40 ` Herbert Xu
2006-04-19 16:07 ` Jesse Brandeburg
2006-04-19 21:29 ` Krzysztof Oledzki
2006-04-19 16:53 ` Stephen Hemminger [this message]
2006-04-19 20:07 ` David S. Miller
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=20060419095348.0de93eaf@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=ak@suse.de \
--cc=bb@kernelpanic.ru \
--cc=cat@zip.com.au \
--cc=chris@scorpion.nl \
--cc=davem@davemloft.net \
--cc=djani22@dynamicweb.hu \
--cc=herbert@gondor.apana.org.au \
--cc=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=jrlundgren@gmail.com \
--cc=kernel@linuxace.com \
--cc=michal@feix.cz \
--cc=mykleb@no.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nipsy@bitgnome.net \
--cc=olel@ans.pl \
--cc=yoseph.basri@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.