Netdev List
 help / color / mirror / Atom feed
From: danborkmann@iogearbox.net
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] af_packet: tpacket_destruct_skb, deref skb after BUG_ON assertion
Date: Mon, 10 Oct 2011 10:02:03 +0200	[thread overview]
Message-ID: <20111010100203.15066m7nvqod58cb@webmail.your-server.de> (raw)
In-Reply-To: <1318193866.21116.3.camel@edumazet-laptop>

Hi Eric,

Quoting Eric Dumazet <eric.dumazet@gmail.com>:
> Le dimanche 09 octobre 2011 à 17:19 +0200, danborkmann@iogearbox.net a
> écrit :
>> This tiny patch derefs the skb only after BUG_ON(skb==NULL) was evaluated
>> and not before. Patched against latest Linus tree.
>>
>> Thanks,
>> Daniel
>>
>> Signed-off-by: Daniel Borkmann <danborkmann@iogearbox.net>
>>
>> diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
>> index fabb4fa..d9d833b 100644
>> --- a/net/packet/af_packet.c
>> +++ b/net/packet/af_packet.c
>> @@ -1167,11 +1167,12 @@ ring_is_full:
>>
>>   static void tpacket_destruct_skb(struct sk_buff *skb)
>>   {
>> -	struct packet_sock *po = pkt_sk(skb->sk);
>> +	struct packet_sock *po;
>>   	void *ph;
>>
>>   	BUG_ON(skb == NULL);
>>
>> +	po = pkt_sk(skb->sk);
>>   	if (likely(po->tx_ring.pg_vec)) {
>>   		ph = skb_shinfo(skb)->destructor_arg;
>>   		BUG_ON(__packet_get_status(po, ph) != TP_STATUS_SENDING);
>>
>>
>
> Well, to be honest, this BUG_ON(!skb) is absolutely useless for two
> reasons.
>
> 1) If skb happens to be NULL, the NULL dereference is trapped and stack
> trace dumped as well.
>
> 2) Of course, tpacket_destruct_skb() being an skb destructor, skb cannot
> be NULL at this point by design.
>
> Please remove the BUG_ON() instead of trying to move it ;)

Thanks, you're absolutely right! Here's the trivial patch:

af_packet: removed unnecessary BUG_ON assertion in tpacket_destruct_skb

If skb is NULL, then stack trace is thrown on anyway on dereference.  
Therefore,
the stack trace triggered by BUG_ON is duplicate.

Signed-off-by: Daniel Borkmann <danborkmann@googlemail.com>

diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
index fabb4fa..886ae50 100644
--- a/net/packet/af_packet.c
+++ b/net/packet/af_packet.c
@@ -1170,8 +1170,6 @@ static void tpacket_destruct_skb(struct sk_buff *skb)
  	struct packet_sock *po = pkt_sk(skb->sk);
  	void *ph;

-	BUG_ON(skb == NULL);
-
  	if (likely(po->tx_ring.pg_vec)) {
  		ph = skb_shinfo(skb)->destructor_arg;
  		BUG_ON(__packet_get_status(po, ph) != TP_STATUS_SENDING);

  reply	other threads:[~2011-10-10  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 15:19 [PATCH] af_packet: tpacket_destruct_skb, deref skb after BUG_ON assertion danborkmann
2011-10-09 20:57 ` Eric Dumazet
2011-10-10  8:02   ` danborkmann [this message]
2011-10-10 16:06     ` Eric Dumazet

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=20111010100203.15066m7nvqod58cb@webmail.your-server.de \
    --to=danborkmann@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --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