kernel-hacking-2024-linux-s.../fs/sysfs
Tejun Heo 41fc1c2745 sysfs: make sysfs_add/remove_one() call link/unlink_sibling() implictly
When adding or removing a sysfs_dirent, the user used to be required
to call link/unlink separately.  It was for two reasons - code looked
like that before sysfs_addrm_cxt conversion and to avoid looping
through parent_sd->children list twice during removal.

Performance optimization during removal just isn't worth it.  Make
sysfs_add/remove_one() call sysfs_link/unlink_sibing() implicitly.
This makes code simpler albeit slightly less efficient.  This change
doesn't introduce any noticeable behavior change.

Signed-off-by: Tejun Heo <htejun@gmail.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2007-10-12 14:51:03 -07:00
..
bin.c sysfs: cleanup semaphore.h 2007-10-12 14:51:03 -07:00
dir.c sysfs: make sysfs_add/remove_one() call link/unlink_sibling() implictly 2007-10-12 14:51:03 -07:00
file.c sysfs: make sysfs_add/remove_one() call link/unlink_sibling() implictly 2007-10-12 14:51:03 -07:00
group.c sysfs: Remove first pass at shadow directory support 2007-10-12 14:51:03 -07:00
inode.c sysfs: make sysfs_add/remove_one() call link/unlink_sibling() implictly 2007-10-12 14:51:03 -07:00
Makefile
mount.c sysfs: Remove first pass at shadow directory support 2007-10-12 14:51:03 -07:00
symlink.c sysfs: make sysfs_add/remove_one() call link/unlink_sibling() implictly 2007-10-12 14:51:03 -07:00
sysfs.h sysfs: make sysfs_add/remove_one() call link/unlink_sibling() implictly 2007-10-12 14:51:03 -07:00