From: Palmer Dabbelt <palmer@sifive.com>
To: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Cc: linux-arch@vger.kernel.org, x86@kernel.org, luto@kernel.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, Arnd Bergmann <arnd@arndb.de>,
Palmer Dabbelt <palmer@sifive.com>
Subject: [PATCH 2/5] Add fchmodat4(), a new syscall
Date: Fri, 31 May 2019 12:12:01 -0700 [thread overview]
Message-ID: <20190531191204.4044-3-palmer@sifive.com> (raw)
In-Reply-To: <20190531191204.4044-1-palmer@sifive.com>
man 3p says that fchmodat() takes a flags argument, but the Linux
syscall does not. There doesn't appear to be a good userspace
workaround for this issue but the implementation in the kernel is pretty
straight-forward. The specific use case where the missing flags came up
was WRT a fuse filesystem implemenation, but the functionality is pretty
generic so I'm assuming there would be other use cases.
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
---
fs/open.c | 21 +++++++++++++++++++--
include/linux/syscalls.h | 5 +++++
2 files changed, 24 insertions(+), 2 deletions(-)
diff --git a/fs/open.c b/fs/open.c
index a00350018a47..cfad7684e8d3 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -568,11 +568,17 @@ SYSCALL_DEFINE2(fchmod, unsigned int, fd, umode_t, mode)
return ksys_fchmod(fd, mode);
}
-int do_fchmodat(int dfd, const char __user *filename, umode_t mode)
+int do_fchmodat4(int dfd, const char __user *filename, umode_t mode, int flags)
{
struct path path;
int error;
- unsigned int lookup_flags = LOOKUP_FOLLOW;
+ unsigned int lookup_flags;
+
+ if (unlikely(flags & ~AT_SYMLINK_NOFOLLOW))
+ return -EINVAL;
+
+ lookup_flags = flags & AT_SYMLINK_NOFOLLOW ? 0 : LOOKUP_FOLLOW;
+
retry:
error = user_path_at(dfd, filename, lookup_flags, &path);
if (!error) {
@@ -586,6 +592,17 @@ int do_fchmodat(int dfd, const char __user *filename, umode_t mode)
return error;
}
+SYSCALL_DEFINE4(fchmodat4, int, dfd, const char __user *, filename,
+ umode_t, mode, int, flags)
+{
+ return do_fchmodat4(dfd, filename, mode, flags);
+}
+
+int do_fchmodat(int dfd, const char __user *filename, umode_t mode)
+{
+ return do_fchmodat4(dfd, filename, mode, 0);
+}
+
SYSCALL_DEFINE3(fchmodat, int, dfd, const char __user *, filename,
umode_t, mode)
{
diff --git a/include/linux/syscalls.h b/include/linux/syscalls.h
index 396871b218f4..cb040a412a4c 100644
--- a/include/linux/syscalls.h
+++ b/include/linux/syscalls.h
@@ -435,6 +435,8 @@ asmlinkage long sys_chroot(const char __user *filename);
asmlinkage long sys_fchmod(unsigned int fd, umode_t mode);
asmlinkage long sys_fchmodat(int dfd, const char __user *filename,
umode_t mode);
+asmlinkage long sys_fchmodat4(int dfd, const char __user *filename,
+ umode_t mode, int flags);
asmlinkage long sys_fchownat(int dfd, const char __user *filename, uid_t user,
gid_t group, int flag);
asmlinkage long sys_fchown(unsigned int fd, uid_t user, gid_t group);
@@ -1315,6 +1317,9 @@ static inline long ksys_link(const char __user *oldname,
extern int do_fchmodat(int dfd, const char __user *filename, umode_t mode);
+extern int do_fchmodat4(int dfd, const char __user *filename, umode_t mode,
+ int flags);
+
static inline int ksys_chmod(const char __user *filename, umode_t mode)
{
return do_fchmodat(AT_FDCWD, filename, mode);
--
2.21.0
next prev parent reply other threads:[~2019-05-31 19:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 19:11 Add a new fchmodat4() syscall Palmer Dabbelt
2019-05-31 19:11 ` Palmer Dabbelt
2019-05-31 19:12 ` [PATCH 1/5] Non-functional cleanup of a "__user * filename" Palmer Dabbelt
2019-05-31 19:12 ` Palmer Dabbelt
2019-05-31 19:12 ` Palmer Dabbelt [this message]
2019-05-31 19:12 ` [PATCH 2/5] Add fchmodat4(), a new syscall Palmer Dabbelt
2019-05-31 19:51 ` Arnd Bergmann
2019-05-31 19:51 ` Arnd Bergmann
2019-05-31 23:36 ` Palmer Dabbelt
2019-05-31 23:36 ` Palmer Dabbelt
2019-05-31 19:12 ` [PATCH 3/5] asm-generic: Register fchmodat4 as syscall 428 Palmer Dabbelt
2019-05-31 19:12 ` Palmer Dabbelt
2019-05-31 19:56 ` Arnd Bergmann
2019-05-31 19:56 ` Arnd Bergmann
2019-05-31 23:57 ` Palmer Dabbelt
2019-05-31 23:57 ` Palmer Dabbelt
2019-05-31 19:12 ` [PATCH 4/5] x86: Add fchmodat4 to syscall_64.tbl Palmer Dabbelt
2019-05-31 19:12 ` Palmer Dabbelt
2019-05-31 19:12 ` [PATCH 5/5] x86: Add fchmod4 to syscall_32.tbl Palmer Dabbelt
2019-05-31 19:12 ` Palmer Dabbelt
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=20190531191204.4044-3-palmer@sifive.com \
--to=palmer@sifive.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/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