netdev - Re: [PATCH v2 net 0/4] bridge: Fix problems around the PVID

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20131018.160342.1865621134607396758.davem@davemloft.net>
Date:	Fri, 18 Oct 2013 16:03:42 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	makita.toshiaki@....ntt.co.jp
Cc:	vyasevic@...hat.com, netdev@...r.kernel.org,
	toshiaki.makita1@...il.com
Subject: Re: [PATCH v2 net 0/4] bridge: Fix problems around the PVID

From: Toshiaki Makita <makita.toshiaki@....ntt.co.jp>
Date: Wed, 16 Oct 2013 17:07:12 +0900

> There seem to be some undesirable behaviors related with PVID.
> 1. It has no effect assigning PVID to a port. PVID cannot be applied
> to any frame regardless of whether we set it or not.
> 2. FDB entries learned via frames applied PVID are registered with
> VID 0 rather than VID value of PVID.
> 3. We can set 0 or 4095 as a PVID that are not allowed in IEEE 802.1Q.
> This leads interoperational problems such as sending frames with VID
> 4095, which is not allowed in IEEE 802.1Q, and treating frames with VID
> 0 as they belong to VLAN 0, which is expected to be handled as they have
> no VID according to IEEE 802.1Q.
 ...
> Patch set follows this mail.
> The order of patches is not the same as described above, because the way
> to fix 1st problem is based on the assumption that we don't use VID 0 as
> a PVID, which is realized by fixing 3rd problem.
> (1/4)(2/4): Fix 3rd problem.
> (3/4): Fix 1st problem.
> (4/4): Fix 2nd probelm.
> 
> v2:
> - Add descriptions about the problem related to priority-tags in cover letter.
> - Revise patch comments to reference the newest spec.

Series applied, thank you.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html