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>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
ff869de7bf
commit
41fc1c2745
@@ -56,8 +56,6 @@ extern struct sysfs_dirent sysfs_root;
|
||||
extern struct kmem_cache *sysfs_dir_cachep;
|
||||
|
||||
extern struct dentry *sysfs_get_dentry(struct sysfs_dirent *sd);
|
||||
extern void sysfs_link_sibling(struct sysfs_dirent *sd);
|
||||
extern void sysfs_unlink_sibling(struct sysfs_dirent *sd);
|
||||
extern struct sysfs_dirent *sysfs_get_active(struct sysfs_dirent *sd);
|
||||
extern void sysfs_put_active(struct sysfs_dirent *sd);
|
||||
extern struct sysfs_dirent *sysfs_get_active_two(struct sysfs_dirent *sd);
|
||||
|
Reference in New Issue
Block a user