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
| ||
|
Date: Fri, 19 Aug 2016 16:59:17 -0700 (PDT) From: David Miller <davem@...emloft.net> To: dmitry.torokhov@...il.com Cc: tj@...nel.org, ebiederm@...ssion.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: [PATCH 0/5] Make /sys/class/net per net namespace objects belong to container From: Dmitry Torokhov <dmitry.torokhov@...il.com> Date: Tue, 16 Aug 2016 15:33:10 -0700 > There are objects in /sys hierarchy (/sys/class/net/) that logically belong > to a namespace/container. Unfortunately all sysfs objects start their life > belonging to global root, and while we could change ownership manually, > keeping tracks of all objects that come and go is cumbersome. It would > be better if kernel created them using correct uid/gid from the beginning. > > This series changes kernfs to allow creating object's with arbitrary > uid/gid, adds get_ownership() callback to ktype structure so subsystems > could supply their own logic (likely tied to namespace support) for > determining ownership of kobjects, and adjusts sysfs code to make use of > this information. Lastly net-sysfs is adjusted to make sure that objects in > net namespace are owned by the root user from the owning user namespace. > > Note that we do not adjust ownership of objects moved into a new namespace > (as when moving a network device into a container) as userspace can easily > do it. I need some domain experts to review this series please. Thank you.
Powered by blists - more mailing lists