[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Mar 2020 17:59:03 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: David Howells <dhowells@...hat.com>
Cc: Miklos Szeredi <miklos@...redi.hu>, Karel Zak <kzak@...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 03, 2020 at 02:19:58PM +0000, David Howells wrote:
> Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
>
> > + fd = do_sys_open(dfd, filename, flags, 0000);
> > + if (fd <= 0)
> > + return fd;
> > +
> > + retval = ksys_read(fd, buffer, bufsize);
> > +
> > + __close_fd(current->files, fd);
>
> If you can use dentry_open() and vfs_read(), you might be able to avoid
> dealing with file descriptors entirely. That might make it worth a syscall.
Will poke at that...
> You're going to be asked for writefile() you know ;-)
Yup, that just got asked on this thread already :)
greg k-h
Powered by blists - more mailing lists