| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090611164111.GC12367@shareable.org> Date: Thu, 11 Jun 2009 17:41:11 +0100 From: Jamie Lokier <jamie@...reable.org> To: Kay Sievers <kay.sievers@...y.org> Cc: Denis Karpov <ext-denis.2.karpov@...ia.com>, hirofumi@...l.parknet.co.jp, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, adrian.hunter@...ia.com, artem.bityutskiy@...ia.com, akpm@...ux-foundation.org Subject: Re: [PATCH 0/5][V2] FS: userspace notification of errors 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-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists