Kay Sievers wrote: > No, the objection was to use the underlying *device* as the source to > raise filesystem events. I don't think there are problems in general > with objects in /sys/fs/ sending events. > > But, the remaining questions here are: > Do we really want superblocks exported in the global, > non-namespace-aware /sys? It might be wrong to export stuff from other > namespaces for filesytems which are irrelevant, and not even visible. > I'm not sure about this, and it needs careful evaluation. We once had > filesystem mount/umount uevents on block devices, and we needed to > remove them for that namespace reason. Is there no namespace awareness in /sys? So how do namespaced guests deal with not having access to /sys, given modern distros make extensive use of it? -- Jamie -- 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