Kay Sievers <kay.sievers@xxxxxxxx> writes: > On Sat, May 23, 2009 at 08:33, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > >> My plan going forward is to fix the ordering problems with deleting >> /sys/dev/char and /sys/dev/block. Add a WARN_ON if we delete a >> non-empty directory. Ensure we don't add something to an already >> deleted directory. > > What's the problem in /sys/dev/? There are just a bunch of symlinks, > one for every device with a dev_t, and all in flat directories, and no > directory to remove. device_shutdown called during reboot removes /sys/dev/block and /sys/dev/char. The current sysfs_remove_dir (because it empties directories) removes all of those symlinks. The problem is that it is the device objects for each individual device that owns those symlinks, and normally removes those symlinks. Which means that in theory we could have double deletion going on. In practice today it doesn't matter because this is at reboot. And as far as that goes it is wrong to remove anything from sysfs during device_shutdown so the fix is just to not call kobject_put there. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
