netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: socketcan@hartkopp.net
Cc: herbert@gondor.apana.org.au, matthias.fuchs@esd.eu,
	netdev@vger.kernel.org, mma@objectxp.com
Subject: Re: problem with 'net: Partially allow skb destructors to be used on receive path'
Date: Wed, 02 Dec 2009 16:00:09 -0800 (PST)	[thread overview]
Message-ID: <20091202.160009.232607094.davem@davemloft.net> (raw)
In-Reply-To: <4B16DA68.3040209@hartkopp.net>

From: Oliver Hartkopp <socketcan@hartkopp.net>
Date: Wed, 02 Dec 2009 22:21:44 +0100

> after a request from Matthias Fuchs regarding the status of this patch in
> 2.6.30-stable, i discovered a problem with the commit in 2.6.30-stable:
> 
> Patch discussion/history: http://patchwork.ozlabs.org/patch/28993/
> 
> The commit in mainline is correct:
 ...
> But the commit in the 2.6.30-stable tree
> 
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commitdiff;h=172570a224fe66d560c097e48fca15b620c76e72
> 
> has a problem in patching include/net/sock.h:
 ...
> The skb_orphan(skb) in skb_set_owner_w() is missing here.
> 
> Is there any chance to fix that in 2.6.30-stable?

Thanks for catching this.  I hate patch :-/

I'll send a fixup patch to the -stable folks right now.

Thanks again!

net: Fix thinko in backport of skb destructor fix.

As noticed by Oliver Hartkopp, the backport of the
'net: Partially allow skb destructors to be used on receive path'
(2.6.30.y commit: 172570a224fe66d560c097e48fca15b620c76e72,
 upstream commit: d55d87fdff8252d0e2f7c28c2d443aee17e9d70f)
was buggy.

It should have added an skb_orphan() call to both skb_set_owner_w()
and skb_set_owner_r().  Instead it added two calls to skb_set_owner_r().

This fixed it up.

Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/include/net/sock.h b/include/net/sock.h
index 9bc2c83..cda3801 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -1223,6 +1223,7 @@ static inline int skb_copy_to_page(struct sock *sk, char __user *from,
 
 static inline void skb_set_owner_w(struct sk_buff *skb, struct sock *sk)
 {
+	skb_orphan(skb);
 	sock_hold(sk);
 	skb->sk = sk;
 	skb->destructor = sock_wfree;
@@ -1232,7 +1233,6 @@ static inline void skb_set_owner_w(struct sk_buff *skb, struct sock *sk)
 static inline void skb_set_owner_r(struct sk_buff *skb, struct sock *sk)
 {
 	skb_orphan(skb);
-	skb_orphan(skb);
 	skb->sk = sk;
 	skb->destructor = sock_rfree;
 	atomic_add(skb->truesize, &sk->sk_rmem_alloc);

      reply	other threads:[~2009-12-03  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 13:17 problem with 'net: Partially allow skb destructors to be used on receive path' Oliver Hartkopp
2009-06-22 12:25 ` Herbert Xu
2009-06-22 13:44   ` Oliver Hartkopp
2009-06-22 14:56     ` Herbert Xu
2009-06-23 23:37       ` David Miller
2009-12-02 21:21         ` Oliver Hartkopp
2009-12-03  0:00           ` David Miller [this message]

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=20091202.160009.232607094.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=matthias.fuchs@esd.eu \
    --cc=mma@objectxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /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).