linux/fs/sysfs
Dmitry Torokhov 5f81880d52 sysfs, kobject: allow creating kobject belonging to arbitrary users
Normally kobjects and their sysfs representation belong to global root,
however it is not necessarily the case for objects in separate namespaces.
For example, objects in separate network namespace logically belong to the
container's root and not global root.

This change lays groundwork for allowing network namespace objects
ownership to be transferred to container's root user by defining
get_ownership() callback in ktype structure and using it in sysfs code to
retrieve desired uid/gid when creating sysfs objects for given kobject.

Co-Developed-by: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2018-07-20 23:44:35 -07:00
..
dir.c sysfs, kobject: allow creating kobject belonging to arbitrary users 2018-07-20 23:44:35 -07:00
file.c sysfs, kobject: allow creating kobject belonging to arbitrary users 2018-07-20 23:44:35 -07:00
group.c sysfs, kobject: allow creating kobject belonging to arbitrary users 2018-07-20 23:44:35 -07:00
Kconfig kernfs: add CONFIG_KERNFS 2014-02-07 16:08:57 -08:00
Makefile sysfs, kernfs: move inode code to fs/kernfs/inode.c 2013-11-29 17:55:10 -08:00
mount.c unfuck sysfs_mount() 2018-05-21 14:30:09 -04:00
symlink.c sysfs: symlink: export sysfs_create_link_nowarn() 2018-03-19 21:14:26 -04:00
sysfs.h sysfs, kobject: allow creating kobject belonging to arbitrary users 2018-07-20 23:44:35 -07:00