[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 03 Mar 2020 15:53:49 +0000
From: David Howells <dhowells@...hat.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: dhowells@...hat.com,
Christian Brauner <christian.brauner@...ntu.com>,
Miklos Szeredi <miklos@...redi.hu>,
Karel Zak <kzak@...hat.com>, Ian Kent <raven@...maw.net>,
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]
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> If you look at the patch I posted in this thread, I think it properly
> supports open_how and RESOLVE_* flags. But remember it's opening a file
> that is already present, in RO mode, no creation allowed, so most of the
> open_how interactions are limited.
Something we should consider adding to openat2() at some point is the ability
to lock on open/create. Various network filesystems support it.
David
Powered by blists - more mailing lists