[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Mar 2020 14:34:42 +0100
From: Miklos Szeredi <miklos@...redi.hu>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Karel Zak <kzak@...hat.com>, David Howells <dhowells@...hat.com>,
Ian Kent <raven@...maw.net>,
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 Tue, Mar 3, 2020 at 2:14 PM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> > Unlimited beers for a 21-line kernel patch? Sign me up!
> >
> > Totally untested, barely compiled patch below.
>
> Ok, that didn't even build, let me try this for real now...
Some comments on the interface:
O_LARGEFILE can be unconditional, since offsets are not exposed to the caller.
Use the openat2 style arguments; limit the accepted flags to sane ones
(e.g. don't let this syscall create a file).
If buffer is too small to fit the whole file, return error.
Verify that the number of bytes read matches the file size, otherwise
return error (may need to loop?).
Thanks,
Miklos
Powered by blists - more mailing lists