[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190529151053.GA10231@kroah.com>
Date: Wed, 29 May 2019 08:10:53 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Jan Kara <jack@...e.cz>
Cc: Amir Goldstein <amir73il@...il.com>,
David Howells <dhowells@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>, Ian Kent <raven@...maw.net>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-api@...r.kernel.org,
linux-block <linux-block@...r.kernel.org>,
keyrings@...r.kernel.org,
LSM List <linux-security-module@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH 0/7] Mount, FS, Block and Keyrings notifications
On Wed, May 29, 2019 at 04:25:04PM +0200, Jan Kara wrote:
> > I am not asking that you implement fs_notify() before merging sb_notify()
> > and I understand that you have a use case for sb_notify().
> > I am asking that you show me the path towards a unified API (how a
> > typical program would look like), so that we know before merging your
> > new API that it could be extended to accommodate fsnotify events
> > where the final result will look wholesome to users.
>
> Are you sure we want to combine notification about file changes etc. with
> administrator-type notifications about the filesystem? To me these two
> sound like rather different (although sometimes related) things.
This patchset is looking to create a "generic" kernel notification
system, so I think the question is valid. It's up to the requestor to
ask for the specific type of notification.
thanks,
greg k-h
Powered by blists - more mailing lists