sysfs: Remove first pass at shadow directory support
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines · Tejun Heo
While shadow directories appear to be a good idea, the current scheme of controlling their creation and destruction outside of sysfs appears to be a locking and maintenance nightmare in the face of sysfs directories dynamically coming and going. Which can now occur for directories containing network devices when
CONFIG_SYSFS_DEPRECATEDis not set.This patch removes everything from the initial shadow directory support that allowed the shadow directory creation to be controlled at a higher level. So except for a few bits of
sysfs_rename_direverything from commitb592fcfe7f06c15ec11774b5be7ce0de3aa86e73is now gone.
"From Eric W. Biederman <[email protected]>" line is missing. I thought git scripts would add that automatically. Sorry about that.
Signature · 1 line
tejun
Hi Tejun,
Quoted 8 lines · Tejun Heo
Quoted 7 lines · Tejun Heo
While shadow directories appear to be a good idea, the current scheme of controlling their creation and destruction outside of sysfs appears to be a locking and maintenance nightmare in the face of sysfs directories dynamically coming and going. Which can now occur for directories containing network devices when
CONFIG_SYSFS_DEPRECATEDis not set.
Quoted 7 lines
Quoted 4 lines
This patch removes everything from the initial shadow directory support that allowed the shadow directory creation to be controlled at a higher level. So except for a few bits of
sysfs_rename_direverything from commitb592fcfe7f06c15ec11774b5be7ce0de3aa86e73is now gone."From Eric W. Biederman <[email protected]>" line is missing. I thought git scripts would add that automatically. Sorry about that.
I couldn't find this patch in the patchset you just posted ...