* Re: [PATCH] fix long-standing bug in 2.6/2.4 skb_copy/skb_copy_expand [not found] <20050508143259.GA30676@shaftnet.org> @ 2005-05-09 3:04 ` Herbert Xu 2005-05-11 20:38 ` Stuffed Crust 0 siblings, 1 reply; 3+ messages in thread From: Herbert Xu @ 2005-05-09 3:04 UTC (permalink / raw) To: Stuffed Crust; +Cc: davem, linux-kernel, netdev Stuffed Crust <pizza@shaftnet.org> wrote: > > This is, fortunately, generally true. But if the alloc_skb function > allocates extra head room (ie calls skb_reserve() on the skb before it > passes it to the callee, this doesn't quite work. Instead, it should be > rewritten as: As far as I know the alloc_skb funciton in the kernel tree doesn't do that so your patch is not necessary unless we decide to change the way alloc_skb works. If that's what you want then please provide a patch to alloc_skb and a rationale as to why we should do that. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] fix long-standing bug in 2.6/2.4 skb_copy/skb_copy_expand 2005-05-09 3:04 ` [PATCH] fix long-standing bug in 2.6/2.4 skb_copy/skb_copy_expand Herbert Xu @ 2005-05-11 20:38 ` Stuffed Crust 2005-05-11 20:56 ` David S. Miller 0 siblings, 1 reply; 3+ messages in thread From: Stuffed Crust @ 2005-05-11 20:38 UTC (permalink / raw) To: Herbert Xu; +Cc: davem, linux-kernel, netdev [-- Attachment #1: Type: text/plain, Size: 1078 bytes --] On Mon, May 09, 2005 at 01:04:34PM +1000, Herbert Xu wrote: > > This is, fortunately, generally true. But if the alloc_skb function > > allocates extra head room (ie calls skb_reserve() on the skb before it > > passes it to the callee, this doesn't quite work. Instead, it should be > > rewritten as: > > As far as I know the alloc_skb funciton in the kernel tree doesn't do > that so your patch is not necessary unless we decide to change the way > alloc_skb works. If that's what you want then please provide a patch > to alloc_skb and a rationale as to why we should do that. It does not, and I have no intention of submitting a patch to change it. As I said in my original message, it was a crude hack which has since been relegated to the great bitbucket of the sky. All that's left is that "bugfix" patch. I've performed my due-diligence in airing it to the powers that be, so I'll go way now. - Solomon -- Solomon Peachy ICQ: 1318344 Melbourne, FL JID: pitha@myjabber.net Quidquid latine dictum sit, altum viditur [-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] fix long-standing bug in 2.6/2.4 skb_copy/skb_copy_expand 2005-05-11 20:38 ` Stuffed Crust @ 2005-05-11 20:56 ` David S. Miller 0 siblings, 0 replies; 3+ messages in thread From: David S. Miller @ 2005-05-11 20:56 UTC (permalink / raw) To: pizza; +Cc: herbert, linux-kernel, netdev From: Stuffed Crust <pizza@shaftnet.org> Subject: Re: [PATCH] fix long-standing bug in 2.6/2.4 skb_copy/skb_copy_expand Date: Wed, 11 May 2005 16:38:45 -0400 > As I said in my original message, it was a crude hack which has since > been relegated to the great bitbucket of the sky. All that's left is > that "bugfix" patch. If alloc_skb() does not do an skb_reserve(), then the bug fix patch is unnecessary. The "bug" only exists if you happen to change alloc_skb() to do an skb_reserve(). ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-05-11 20:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20050508143259.GA30676@shaftnet.org>
2005-05-09 3:04 ` [PATCH] fix long-standing bug in 2.6/2.4 skb_copy/skb_copy_expand Herbert Xu
2005-05-11 20:38 ` Stuffed Crust
2005-05-11 20:56 ` David S. Miller
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).