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
| ||
|
Message-ID: <cc6c7118-95f0-5252-4962-b4376b4bf61d@gmail.com> Date: Mon, 8 May 2017 10:26:59 -0700 From: Florian Fainelli <f.fainelli@...il.com> To: David Ahern <dsahern@...il.com>, netdev@...r.kernel.org Cc: roopa@...ulusnetworks.com, nicolas.dichtel@...nd.com Subject: Re: [PATCH RFC net-next 4/6] net: Do not intialize kobject for lightweight netdevs On 05/06/2017 09:07 AM, David Ahern wrote: > Lightweight netdevices are not added to sysfs; bypass kobject > initialization. I was wondering if we actually needed a flag to tell: this is a lightweight device, but still let it show up in /sys. All use cases that I have in mind (getting the physical port name etc. etc) can be done via netlink which is not restricted even with LWT devices, so this sounds reasonable. In case we need to revisit that, we can always add more flags to control the lightweight devices creation and how this percolates through the networking stack. Thanks! -- Florian
Powered by blists - more mailing lists