From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: [git pull] vfs.git mount compat series
Date: Mon, 12 Oct 2020 04:27:48 +0100 [thread overview]
Message-ID: <20201012032748.GH3576660@ZenIV.linux.org.uk> (raw)
The last remnants of mount(2) compat buried. Buried into NFS, that is;
generally I'm less enthusiastic about "let's use in_compat_syscall() deep in
call chain" kind of approach than Christoph seems to be, but in this case it's
warranted - that crap had been an NFS-specific wart, hopefully not to be repeated
in any other filesystems (read: any new filesystem introducing non-text mount
options will get NAKed even if it doesn't fuck the layout up). Not worth trying
to grow an infrastructure that would avoid that use of in_compat_syscall()...
[Note: alpha-related tail of the series got dropped]
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git compat.mount
for you to fetch changes up to 028abd9222df0cf5855dab5014a5ebaf06f90565:
fs: remove compat_sys_mount (2020-09-22 23:45:57 -0400)
----------------------------------------------------------------
Christoph Hellwig (3):
nfs: simplify nfs4_parse_monolithic
fs,nfs: lift compat nfs4 mount data handling into the nfs code
fs: remove compat_sys_mount
arch/arm64/include/asm/unistd32.h | 2 +-
arch/mips/kernel/syscalls/syscall_n32.tbl | 2 +-
arch/mips/kernel/syscalls/syscall_o32.tbl | 2 +-
arch/parisc/kernel/syscalls/syscall.tbl | 2 +-
arch/powerpc/kernel/syscalls/syscall.tbl | 2 +-
arch/s390/kernel/syscalls/syscall.tbl | 2 +-
arch/sparc/kernel/syscalls/syscall.tbl | 2 +-
arch/x86/entry/syscalls/syscall_32.tbl | 2 +-
fs/Makefile | 1 -
fs/compat.c | 132 --------------
fs/internal.h | 3 -
fs/namespace.c | 4 +-
fs/nfs/fs_context.c | 195 +++++++++++++--------
include/linux/compat.h | 6 -
include/uapi/asm-generic/unistd.h | 2 +-
tools/include/uapi/asm-generic/unistd.h | 2 +-
tools/perf/arch/powerpc/entry/syscalls/syscall.tbl | 2 +-
tools/perf/arch/s390/entry/syscalls/syscall.tbl | 2 +-
18 files changed, 138 insertions(+), 227 deletions(-)
delete mode 100644 fs/compat.c
next reply other threads:[~2020-10-12 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 3:27 Al Viro [this message]
2020-10-12 23:50 ` [git pull] vfs.git mount compat series 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=20201012032748.GH3576660@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--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