Messages in this thread | | | From | Kay Sievers <> | Date | Thu, 11 Jun 2009 18:43:46 +0200 | Subject | Re: [PATCH 0/5][V2] FS: userspace notification of errors |
| |
On Thu, Jun 11, 2009 at 18:41, Jamie Lokier<jamie@shareable.org> wrote: > 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?
No, not at all. It is the straight export of the core kernel objects.
> So how do namespaced guests deal with not having access to /sys, given > modern distros make extensive use of it?
They ignore it and don't use it, or get confused, I guess. :)
Thanks, Kay
| |