From: Greg KH <greg@kroah.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: stable@kernel.org, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [stable] [NET]: Update frag_list in pskb_trim
Date: Mon, 17 Jul 2006 08:22:44 -0700 [thread overview]
Message-ID: <20060717152244.GA2174@kroah.com> (raw)
In-Reply-To: <20060715001003.GD9334@gondor.apana.org.au>
On Sat, Jul 15, 2006 at 10:10:03AM +1000, Herbert Xu wrote:
> On Thu, Jul 13, 2006 at 10:05:26PM -0700, David Miller wrote:
> >
> > As I noted already, this is in my tree and will go off to
> > Linus soon.
> >
> > Please toss this over to -stable under seperate cover, if
> > you haven't done so already. Please add my signoff:
> >
> > Signed-off-by: David S. Miller <davem@davemloft.net>
>
> Great. Here we go:
>
> [NET]: Update frag_list in pskb_trim
>
> When pskb_trim has to defer to ___pksb_trim to trim the frag_list part of
> the packet, the frag_list is not updated to reflect the trimming. This
> will usually work fine until you hit something that uses the packet length
> or tail from the frag_list.
>
> Examples include esp_output and ip_fragment.
Ick, this doesn't apply to 2.6.17, care to rediff it? I don't trust
myself to get it correct :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-07-17 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 9:03 [NET]: Update frag_list in pskb_trim Herbert Xu
2006-07-14 2:22 ` David Miller
2006-07-14 5:05 ` David Miller
2006-07-15 0:10 ` Herbert Xu
2006-07-17 15:22 ` Greg KH [this message]
2006-07-17 18:13 ` [stable] " Herbert Xu
2006-07-30 22:50 ` Herbert Xu
2006-08-03 7:19 ` Greg KH
2006-07-29 11:45 ` [NET]: Fix ___pskb_trim when entire frag_list needs dropping Herbert Xu
2006-07-30 22:46 ` David Miller
2006-08-02 15:01 ` Marco Berizzi
2006-08-02 21:15 ` David 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=20060717152244.GA2174@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=stable@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).