netdev - Re: [RFC RTNETLINK 04/09]: Link creation API

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]

Message-ID: <20070605161618.2328c6c4@freepuppy>
Date:	Tue, 5 Jun 2007 16:16:18 -0700
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	netdev@...r.kernel.org, socketcan@...tkopp.net, hadi@...erus.ca,
	xemul@...ru, ebiederm@...ssion.com, tgraf@...g.ch
Subject: Re: [RFC RTNETLINK 04/09]: Link creation API

On Wed, 06 Jun 2007 01:17:11 +0200
Patrick McHardy <kaber@...sh.net> wrote:

> Stephen Hemminger wrote:
> > On Tue,  5 Jun 2007 16:12:57 +0200 (MEST)
> > Patrick McHardy <kaber@...sh.net> wrote:
> > 
> > 
> >>[RTNETLINK]: Link creation API
> >>
> >>Add rtnetlink API for creating, changing and deleting software devices.
> >>
> >>Signed-off-by: Patrick McHardy <kaber@...sh.net>
> >>
> > 
> > If you want I'll extend existing bridge netlink to use these.
> 
> 
> Are you talking about brige-port information or bridge device
> configuration? So far the API is not suitable for anything that
> currently uses IFLA_PROTINFO because the sender is not the driver
> which created the device and doesn't use AF_UNSPEC. For bridge
> device configuration it would certainly be nice to have, but I'm
> not sure yet how to handle enslave operations. So far my favourite
> idea is to add enslave/release operations to rtnl_link_ops and call
> them when IFLA_MASTER is set (so the netlink message would look like
> this: ifindex: eth0 master: br0 nlmsg_type: RTM_NETLINK). But I
> haven't really thought this through yet.

Was thinking AF_BRIDGE (we have it already so use it), and both
add/remove bridge, and enslave/unslave device.


> I would also like to add support for handling "secondary device state"
> like bridge port state and others that currently use IFLA_PROTINFO
> (a lot of the code is very similar to the generic code), but all ideas
> so far turned out not to work very well.
> 
> I'm leaving for a short vacation until Sunday tommorrow, so replies
> may be delayed :)


-- 
Stephen Hemminger <shemminger@...ux-foundation.org>
-
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