netdev - Re: [PATCH net-next v5 1/3] bridge: new mode flag to indicate mode 'undefined'

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]

Date:	Tue, 9 Dec 2014 08:54:28 +0100
From:	Jiri Pirko <jiri@...nulli.us>
To:	roopa@...ulusnetworks.com
Cc:	sfeldma@...il.com, jhs@...atatu.com, bcrl@...ck.org, tgraf@...g.ch,
	john.fastabend@...il.com, stephen@...workplumber.org,
	linville@...driver.com, vyasevic@...hat.com,
	netdev@...r.kernel.org, davem@...emloft.net,
	shm@...ulusnetworks.com, gospo@...ulusnetworks.com
Subject: Re: [PATCH net-next v5 1/3] bridge: new mode flag to indicate mode
 'undefined'

Mon, Dec 08, 2014 at 11:04:19PM CET, roopa@...ulusnetworks.com wrote:
>From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
>This patch adds mode BRIDGE_MODE_UNDEF for cases where mode is not needed.
>
>Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>

Signed-off-by: Jiri Pirko <jiri@...nulli.us>

>
>---
> include/uapi/linux/if_bridge.h |    1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/include/uapi/linux/if_bridge.h b/include/uapi/linux/if_bridge.h
>index 296a556..05f0869 100644
>--- a/include/uapi/linux/if_bridge.h
>+++ b/include/uapi/linux/if_bridge.h
>@@ -106,6 +106,7 @@ struct __fdb_entry {
> #define BRIDGE_MODE_VEB		0	/* Default loopback mode */
> #define BRIDGE_MODE_VEPA	1	/* 802.1Qbg defined VEPA mode */
> #define BRIDGE_MODE_SWDEV	2	/* Full switch device offload */
>+#define BRIDGE_MODE_UNDEF	0xFFFF  /* mode undefined */
> 
> /* Bridge management nested attributes
>  * [IFLA_AF_SPEC] = {
>-- 
>1.7.10.4
>
--
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