[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200307094834.GA3888906@kroah.com>
Date: Sat, 7 Mar 2020 10:48:34 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Ian Kent <raven@...maw.net>, David Howells <dhowells@...hat.com>,
Christian Brauner <christian.brauner@...ntu.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Miklos Szeredi <mszeredi@...hat.com>,
viro <viro@...iv.linux.org.uk>,
Christian Brauner <christian@...uner.io>,
Jann Horn <jannh@...gle.com>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Linux API <linux-api@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/17] VFS: Filesystem information and notifications [ver
#17]
On Fri, Mar 06, 2020 at 05:25:49PM +0100, Miklos Szeredi wrote:
> On Tue, Mar 03, 2020 at 08:46:09AM +0100, Miklos Szeredi wrote:
> >
> > I'm doing a patch. Let's see how it fares in the face of all these
> > preconceptions.
>
> Here's a first cut. Doesn't yet have superblock info, just mount info.
> Probably has rough edges, but appears to work.
>
> I started with sysfs, then kernfs, then went with a custom filesystem, because
> neither could do what I wanted.
Hm, what is wrong with kernfs that prevented you from using it here?
Just complexity or something else?
thanks,
greg k-h
Powered by blists - more mailing lists