From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: viro@zeniv.linux.org.uk, mtk.manpages@gmail.com,
shuah@kernel.org, linux-api@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-man@vger.kernel.org, linux-kselftest@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH 1/3] readfile: implement readfile syscall
Date: Sat, 4 Jul 2020 16:02:47 +0200 [thread overview]
Message-ID: <20200704140250.423345-2-gregkh@linuxfoundation.org> (raw)
In-Reply-To: <20200704140250.423345-1-gregkh@linuxfoundation.org>
It's a tiny syscall, meant to allow a user to do a single "open this
file, read into this buffer, and close the file" all in a single shot.
Should be good for reading "tiny" files like sysfs, procfs, and other
"small" files.
There is no restarting the syscall, this is a "simple" syscall, with the
attempt to make reading "simple" files easier with less syscall
overhead.
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
fs/open.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
diff --git a/fs/open.c b/fs/open.c
index 6cd48a61cda3..4469faa9379c 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -1370,3 +1370,53 @@ int stream_open(struct inode *inode, struct file *filp)
}
EXPORT_SYMBOL(stream_open);
+
+static struct file *readfile_open(int dfd, const char __user *filename,
+ struct open_flags *op)
+{
+ struct filename *tmp;
+ struct file *f;
+
+ tmp = getname(filename);
+ if (IS_ERR(tmp))
+ return (struct file *)tmp;
+
+ f = do_filp_open(dfd, tmp, op);
+ if (!IS_ERR(f))
+ fsnotify_open(f);
+
+ putname(tmp);
+ return f;
+}
+
+SYSCALL_DEFINE5(readfile, int, dfd, const char __user *, filename,
+ char __user *, buffer, size_t, bufsize, int, flags)
+{
+ struct open_flags op;
+ struct open_how how;
+ struct file *file;
+ loff_t pos = 0;
+ int retval;
+
+ /* only accept a small subset of O_ flags that make sense */
+ if ((flags & (O_NOFOLLOW | O_NOATIME)) != flags)
+ return -EINVAL;
+
+ /* add some needed flags to be able to open the file properly */
+ flags |= O_RDONLY | O_LARGEFILE;
+
+ how = build_open_how(flags, 0000);
+ retval = build_open_flags(&how, &op);
+ if (retval)
+ return retval;
+
+ file = readfile_open(dfd, filename, &op);
+ if (IS_ERR(file))
+ return PTR_ERR(file);
+
+ retval = vfs_read(file, buffer, bufsize, &pos);
+
+ filp_close(file, NULL);
+
+ return retval;
+}
--
2.27.0
next prev parent reply other threads:[~2020-07-04 14:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 14:02 [PATCH 0/3] readfile(2): a new syscall to make open/read/close faster Greg Kroah-Hartman
2020-07-04 14:02 ` Greg Kroah-Hartman [this message]
2020-07-04 18:35 ` [PATCH 1/3] readfile: implement readfile syscall Geert Uytterhoeven
2020-07-04 19:14 ` Matthew Wilcox
2020-07-04 19:41 ` Miklos Szeredi
2020-07-04 20:12 ` Al Viro
2020-07-04 20:16 ` Al Viro
2020-07-04 14:02 ` [PATCH 2/3] arch: wire up the " Greg Kroah-Hartman
2020-07-04 18:36 ` Geert Uytterhoeven
2020-07-04 14:02 ` [PATCH 3/3] selftests: add readfile(2) selftests Greg Kroah-Hartman
2020-07-04 18:38 ` Geert Uytterhoeven
2020-07-05 6:55 ` Greg Kroah-Hartman
2020-07-05 11:24 ` Geert Uytterhoeven
2020-07-05 11:36 ` Greg Kroah-Hartman
2020-07-05 1:41 ` Heinrich Schuchardt
2020-07-05 7:34 ` Greg Kroah-Hartman
2020-07-05 9:46 ` Heinrich Schuchardt
2020-07-04 14:02 ` [PATCH] readfile.2: new page describing readfile(2) Greg Kroah-Hartman
2020-07-05 2:54 ` Heinrich Schuchardt
2020-07-04 19:30 ` [PATCH 0/3] readfile(2): a new syscall to make open/read/close faster Al Viro
2020-07-05 11:47 ` Greg Kroah-Hartman
2020-07-06 17:25 ` Dave Martin
2020-07-04 20:50 [PATCH 1/3] readfile: implement readfile syscall Alexey Dobriyan
2020-07-04 21:15 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200704140250.423345-2-gregkh@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).