From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] vfs.git mount followups
Date: Fri, 17 May 2019 04:11:26 +0100 [thread overview]
Message-ID: <20190517031125.GF17978@ZenIV.linux.org.uk> (raw)
Propagation of new syscalls to other architectures + cosmetical
change from Christian (fscontext didn't follow the convention for anon
inode names).
What is _not_ included is cloexec changes - I really don't see
the benefits for the cloexec-by-default for new syscalls, when there's
no chance in hell of switching to that policy for old ones.
The following changes since commit 05883eee857eab4693e7d13ebab06716475c5754:
do_move_mount(): fix an unsafe use of is_anon_ns() (2019-05-09 02:32:50 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git fixes
for you to fetch changes up to d8076bdb56af5e5918376cd1573a6b0007fc1a89:
uapi: Wire up the mount API syscalls on non-x86 arches [ver #2] (2019-05-16 12:23:45 -0400)
----------------------------------------------------------------
Christian Brauner (1):
uapi, fsopen: use square brackets around "fscontext" [ver #2]
David Howells (2):
uapi, x86: Fix the syscall numbering of the mount API syscalls [ver #2]
uapi: Wire up the mount API syscalls on non-x86 arches [ver #2]
arch/alpha/kernel/syscalls/syscall.tbl | 6 ++++++
arch/arm/tools/syscall.tbl | 6 ++++++
arch/arm64/include/asm/unistd.h | 2 +-
arch/arm64/include/asm/unistd32.h | 12 ++++++++++++
arch/ia64/kernel/syscalls/syscall.tbl | 6 ++++++
arch/m68k/kernel/syscalls/syscall.tbl | 6 ++++++
arch/microblaze/kernel/syscalls/syscall.tbl | 6 ++++++
arch/mips/kernel/syscalls/syscall_n32.tbl | 6 ++++++
arch/mips/kernel/syscalls/syscall_n64.tbl | 6 ++++++
arch/mips/kernel/syscalls/syscall_o32.tbl | 6 ++++++
arch/parisc/kernel/syscalls/syscall.tbl | 6 ++++++
arch/powerpc/kernel/syscalls/syscall.tbl | 6 ++++++
arch/s390/kernel/syscalls/syscall.tbl | 6 ++++++
arch/sh/kernel/syscalls/syscall.tbl | 6 ++++++
arch/sparc/kernel/syscalls/syscall.tbl | 6 ++++++
arch/x86/entry/syscalls/syscall_32.tbl | 12 ++++++------
arch/x86/entry/syscalls/syscall_64.tbl | 12 ++++++------
arch/xtensa/kernel/syscalls/syscall.tbl | 6 ++++++
fs/fsopen.c | 2 +-
include/uapi/asm-generic/unistd.h | 14 +++++++++++++-
20 files changed, 123 insertions(+), 15 deletions(-)
next reply other threads:[~2019-05-17 3:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 3:11 Al Viro [this message]
2019-05-17 18:35 ` [git pull] vfs.git mount followups pr-tracker-bot
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=20190517031125.GF17978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).