netdev - Re: [patch net-next 0/5] bridge: implement rtnl_link options for getting and setting bridge options

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 5 Sep 2014 10:06:07 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Jiri Pirko <jiri@...nulli.us>
Cc:	netdev@...r.kernel.org, davem@...emloft.net,
	sfeldma@...ulusnetworks.com, arvid.brodin@...en.se,
	sucheta.chakraborty@...gic.com
Subject: Re: [patch net-next 0/5] bridge: implement rtnl_link options for
 getting and setting bridge options

On Fri,  5 Sep 2014 15:51:27 +0200
Jiri Pirko <jiri@...nulli.us> wrote:

> So far, only sysfs is complete interface for getting and setting bridge
> options. This patchset follows-up on the similar bonding code and
> allows userspace to get/set bridge master/port options using Netlink
> IFLA_INFO_DATA/IFLA_INFO_SLAVE_DATA attr.
> 
> Jiri Pirko (5):
>   bridge: switch order of rx_handler reg and upper dev link
>   bridge: implement rtnl_link_ops->get_slave_size and
>     rtnl_link_ops->fill_slave_info
>   bridge: implement rtnl_link_ops->slave_changelink
>   bridge: implement rtnl_link_ops->get_size and rtnl_link_ops->fill_info
>   bridge: implement rtnl_link_ops->changelink
> 
>  include/uapi/linux/if_link.h |  12 +++++
>  net/bridge/br_if.c           |  15 +++---
>  net/bridge/br_netlink.c      | 109 +++++++++++++++++++++++++++++++++++++++----
>  3 files changed, 121 insertions(+), 15 deletions(-)
> 

Looks good, I will try and go over in more detail and look for
any specific issues.
--
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