From: Vlad Yasevich <vyasevic@redhat.com>
To: David Miller <davem@davemloft.net>, makita.toshiaki@lab.ntt.co.jp
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [PATCH net] bridge: Prevent insertion of FDB entry with disallowed vlan
Date: Mon, 02 Jun 2014 10:22:10 -0400 [thread overview]
Message-ID: <538C8892.8030800@redhat.com> (raw)
In-Reply-To: <20140530.154857.23436038195529720.davem@davemloft.net>
On 05/30/2014 06:48 PM, David Miller wrote:
> From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
> Date: Mon, 26 May 2014 15:15:53 +0900
>
>> br_handle_local_finish() is allowing us to insert an FDB entry with
>> disallowed vlan. For example, when port 1 and 2 are communicating in
>> vlan 10, and even if vlan 10 is disallowed on port 3, port 3 can
>> interfere with their communication by spoofed src mac address with
>> vlan id 10.
>>
>> Note: Even if it is judged that a frame should not be learned, it should
>> not be dropped because it is destined for not forwarding layer but higher
>> layer. See IEEE 802.1Q-2011 8.13.10.
>>
>> Signed-off-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
>
> In reference to Vlad's suggestion to try to reuse the logic of the
> existing br_allowed_ingress() function, I don't think that's so
> easy.
>
> As stated already, it drops packets whilst we don't want that here.
>
> Another difference is that it does vlan_untag(), which we also do
> not want here.
>
> Let's just stay with this version of the fix, Vlad if you're OK with
> that can you please give your ACK? Thanks.
>
Acked-by: Vlad Yasevich <vyasevic@redhat.com>
I need to spend a little time and figure out how to make it more re-usable.
-vlad
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevic@redhat.com>
To: David Miller <davem@davemloft.net>, makita.toshiaki@lab.ntt.co.jp
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: [PATCH net] bridge: Prevent insertion of FDB entry with disallowed vlan
Date: Mon, 02 Jun 2014 10:22:10 -0400 [thread overview]
Message-ID: <538C8892.8030800@redhat.com> (raw)
In-Reply-To: <20140530.154857.23436038195529720.davem@davemloft.net>
On 05/30/2014 06:48 PM, David Miller wrote:
> From: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
> Date: Mon, 26 May 2014 15:15:53 +0900
>
>> br_handle_local_finish() is allowing us to insert an FDB entry with
>> disallowed vlan. For example, when port 1 and 2 are communicating in
>> vlan 10, and even if vlan 10 is disallowed on port 3, port 3 can
>> interfere with their communication by spoofed src mac address with
>> vlan id 10.
>>
>> Note: Even if it is judged that a frame should not be learned, it should
>> not be dropped because it is destined for not forwarding layer but higher
>> layer. See IEEE 802.1Q-2011 8.13.10.
>>
>> Signed-off-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
>
> In reference to Vlad's suggestion to try to reuse the logic of the
> existing br_allowed_ingress() function, I don't think that's so
> easy.
>
> As stated already, it drops packets whilst we don't want that here.
>
> Another difference is that it does vlan_untag(), which we also do
> not want here.
>
> Let's just stay with this version of the fix, Vlad if you're OK with
> that can you please give your ACK? Thanks.
>
Acked-by: Vlad Yasevich <vyasevic@redhat.com>
I need to spend a little time and figure out how to make it more re-usable.
-vlad
next prev parent reply other threads:[~2014-06-02 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 6:15 [Bridge] [PATCH net] bridge: Prevent insertion of FDB entry with disallowed vlan Toshiaki Makita
2014-05-26 6:15 ` Toshiaki Makita
2014-05-28 14:02 ` [Bridge] " Vlad Yasevich
2014-05-28 14:02 ` Vlad Yasevich
2014-05-28 14:32 ` [Bridge] " Toshiaki Makita
2014-05-28 14:32 ` Toshiaki Makita
2014-05-30 22:48 ` David Miller
2014-05-30 22:48 ` David Miller
2014-06-02 14:22 ` Vlad Yasevich [this message]
2014-06-02 14:22 ` Vlad Yasevich
2014-06-02 20:38 ` [Bridge] " David Miller
2014-06-02 20:38 ` David Miller
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=538C8892.8030800@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.