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
| ||
|
Date: Tue, 19 Nov 2013 12:36:21 +1100 From: Dave Chinner <david@...morbit.com> To: Christoph Hellwig <hch@...radead.org> Cc: Dmitry Monakhov <dmonakhov@...nvz.org>, linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH] ext4: add generic uevent infrastructure On Mon, Nov 18, 2013 at 08:20:45AM -0800, Christoph Hellwig wrote: > On Mon, Nov 18, 2013 at 06:38:40PM +0400, Dmitry Monakhov wrote: > > *Purpose: > > It is reasonable to annaunce fs related events via uevent infrastructure. > > This patch implement only ext4'th part, but IMHO this should be usefull for > > any generic filesystem. > > It does indeed look very generic. How about you try to redo it to sit > at the VFS level? I certain agree with that. I'd also like to see ENOSPC notifications as that would obliviate the need for distros like RHEL to ship systemtap scripts to generate such notifications for admins.... > Also Jan Kara has done quota netlink notifications a while ago, which > fit into the same sort of niche. The question I'm asking is whether we really want a new interface for these events? Shouldn't we really try to use an existing filesystem event interface for generating these events (e.g. fanotify) rather than adding yet another disjoint filesystem event interface to the kernel? Cheers, Dave. -- Dave Chinner david@...morbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists