Kay Sievers wrote:
And I don't think we want several event sources for the same thing, uevents _and_ pollable sysfs files. We already raise events on /proc/self/mountinfo when the mount tree changes, I guess that's where fs specific stuff belongs, and it will work with all kind of filesystem setups, regardless of the devices below it. This is also the established interface for flags and options and the current state of the filesystem, and does not mix filesystem options into block device interfaces. /proc/self/mountinfo could also work properly with namespaces which might have different meaning for a device in a different namespace.
Well, Denis suggests /sys/fs instead. But how would we pass stuff like error code via /proc/self/mountinfo? And what if later some one wants to provide user-space stuff like bogus inode number? IMO, /sys/fs sounds better. -- Best Regards, Artem Bityutskiy (Артём Битюцкий) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
