netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
To: vyasevic@redhat.com
Cc: Toshiaki Makita <toshiaki.makita1@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net] bridge: Fix crash with vlan filtering and tcpdump
Date: Tue, 07 Jan 2014 21:52:47 +0900	[thread overview]
Message-ID: <1389099167.3768.19.camel@ubuntu-vm-makita> (raw)
In-Reply-To: <52CAD39A.7040607@redhat.com>

On Mon, 2014-01-06 at 11:02 -0500, Vlad Yasevich wrote:
> On 01/05/2014 10:02 AM, Toshiaki Makita wrote:
> > On Fri, 2014-01-03 at 11:12 -0500, Vlad Yasevich wrote:
> >> When the vlan filtering is enabled on the bridge, but
> >> the filter is not configured on the bridge device itself,
> >> running tcpdump on the bridge device will result in a
> >> an Ooops with NULL pointer dereference.  The reason
> >     ^^^^^
> > Oops?
> > 
> >> is that br_pass_frame_up() will bypass the vlan
> >> check because promisc flag is set.  It will then try
> >> to get the table pointer and process the packet based
> >> on the table.  Since the table pointer is NULL, we oops.
> >> Catch this special condition in br_handle_vlan().
> >>
> >> Reported-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
> >> CC: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
> >> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
> >> ---
> > ...
> >> diff --git a/net/bridge/br_vlan.c b/net/bridge/br_vlan.c
> >> index af5ebd1..ea0c29b 100644
> >> --- a/net/bridge/br_vlan.c
> >> +++ b/net/bridge/br_vlan.c
> >> @@ -144,6 +144,18 @@ struct sk_buff *br_handle_vlan(struct net_bridge *br,
> >>  	if (!br->vlan_enabled)
> >>  		goto out;
> >>  
> >> +	/* Vlan filter table must be configrured at this point.  The
> >> +	 * only exception is the bridge is set in promisc mode and the
> >> +	 * packet is destined for the bridge device.  In this case
> >> +	 * pass the packet as is.
> >> +	 */
> >> +	if (!pv) {
> >> +       		if ((br->dev->flags & IFF_PROMISC) && skb->dev == br->dev)
> >> +			goto out;
> > 
> > Currently this function is calling __vlan_put_tag() if port_idx==0.
> > You are going to bypass it only if br is promisc mode.
> > 
> > However it doesn't seem to lead any problem because
> > __netif_receive_skb_core() can handle hw accel vlan tag.
> > 
> > Instead, I doubt if __vlan_put_tag() is necessary in br_handle_vlan()...
> 
> I'll need to re-test, but I remember having had to add that code to make
> it work on the bridge...
> 
> Looking at it again, I agree that special handling for forwarding to the
> bridge doesn't seem to be needed.
> 

Then, I'm OK with that "goto" statement :)

One more comment:
How about using BUG_ON() instead of "if-else BUG()"?
I think it could make the code slightly more efficient and simple.

Thanks,
Toshiaki Makita

      reply	other threads:[~2014-01-07 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 16:12 [PATCH net] bridge: Fix crash with vlan filtering and tcpdump Vlad Yasevich
2014-01-03 18:06 ` Sergei Shtylyov
2014-01-03 17:41   ` Vlad Yasevich
2014-01-05 15:02 ` Toshiaki Makita
2014-01-06 16:02   ` Vlad Yasevich
2014-01-07 12:52     ` Toshiaki Makita [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=1389099167.3768.19.camel@ubuntu-vm-makita \
    --to=makita.toshiaki@lab.ntt.co.jp \
    --cc=netdev@vger.kernel.org \
    --cc=toshiaki.makita1@gmail.com \
    --cc=vyasevic@redhat.com \
    /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).