netdev - Re: [PATCH] Notify userspace about bridge learning MAC on new port

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: <20140317.215005.1881170250001094391.davem@davemloft.net>
Date:	Mon, 17 Mar 2014 21:50:05 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	michael-dev@...i-braun.de
Cc:	stephen@...workplumber.org, bridge@...ts.linux-foundation.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH] Notify userspace about bridge learning MAC on new port

From: Michael Braun <michael-dev@...i-braun.de>
Date: Wed, 12 Mar 2014 14:14:56 +0100

> Currently, the userspace is informed about the port the MAC is learned on a
> bridge and about the bridge removing the MAC from its forwarding table, but not
> when the MAC is learned on a different port.
> This is inconsistent and makes it difficult for applications to keep track
> of all MACs learned by a bridge on a subset of its ports.
> 
> Signed-off-by: Michael Braun <michael-dev@...i-braun.de>
> Acked-by: Roopa Prabhu <roopa@...ulusnetworks.com>

Please use a proper subsystem prefix in your Subject lines, for
example:

"Subject: [PATCH] bridge: Notify userspace about learning MAC on new port"

Would have been more appropriate here.

Stephen, can you review the substance of this patch please?
--
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