From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andrey Utkin <andrey.krieger.utkin@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
acme@ghostprotocols.net, netdev@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] appletalk: Set skb with destructor
Date: Mon, 07 Jul 2014 10:57:36 +0200 [thread overview]
Message-ID: <1404723456.4501.14.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CANZNk81v7YHKpzjZ65KHdUi1BgBiV_ibZO24b8uauuCVZeUv2A@mail.gmail.com>
On Mon, 2014-07-07 at 11:03 +0300, Andrey Utkin wrote:
> 2014-07-07 0:42 GMT+03:00 Eric Dumazet <eric.dumazet@gmail.com>:
> >> /* Queue packet (standard) */
> >> + sock_hold(sock);
> >> + skb->destructor = atalk_skb_destructor;
> >> skb->sk = sock;
> >
> > This part is not needed : sock_queue_rcv_skb() already does the right
> > thing : It calls skb_set_owner_r(skb, sk);
> >
> > You should therefore remove the "skb->sk = sock;" line
>
> If it is so, i think this should be as another patch with its own reasoning.
>
No it is not.
Its illegal to set skb->sk to a socket without taking proper reference.
But it is useless to do this before calling sock_queue_rcv_skb(), as I
explained to you.
This is adding two extra atomic operations for nothing: skb_orphan() is
called from sock_queue_rcv_skb(), so it is kind of stupid to set a
destructor that _will_ be immediately called.
We do not do defensive programming, we try to do logical things, and
only logical things.
Please re-spin your patch, by integrating my feedback.
Thanks !
next prev parent reply other threads:[~2014-07-07 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 4:28 Andrey Utkin
2014-07-05 20:28 ` Dan Carpenter
2014-07-06 11:56 ` Andrey Utkin
2014-07-06 21:42 ` Eric Dumazet
2014-07-07 8:03 ` Andrey Utkin
2014-07-07 8:57 ` Eric Dumazet [this message]
2014-07-07 9:26 ` Eric Dumazet
2014-07-07 10:02 ` Andrey Utkin
2014-07-07 16:56 ` Eric Dumazet
2014-07-07 18:57 ` Andrey Utkin
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=1404723456.4501.14.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=andrey.krieger.utkin@gmail.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®