From: Al Viro <viro@zeniv.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
David Laight <David.Laight@aculab.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, X86 ML <x86@kernel.org>
Subject: Re: in_compat_syscall() on x86
Date: Wed, 6 Jan 2021 00:30:16 +0000 [thread overview]
Message-ID: <20210106003016.GZ3579531@ZenIV.linux.org.uk> (raw)
In-Reply-To: <878s97aq4c.fsf@x220.int.ebiederm.org>
On Tue, Jan 05, 2021 at 06:03:15PM -0600, Eric W. Biederman wrote:
> > Yes, the current mainline is bloody awful in that area (PRSTATUS_SIZE and
> > SET_PR_FPVALID are not for weak stomach), but that's really not hard to
> > get into sane shape - -next had that done in last cycle and I'm currently
> > testing (well, building the test kernel) of port of that to 5.11-rc1.
>
> That does sound interesting. Anytime we can clean up arch specific
> weirdness so that it simply becomes generic weirdness and it can be
> tested and maintained by more people is always nice.
vfs.git #work.elf-compat, and AFAICS it works.
arch/Kconfig | 3 ++
arch/arm64/Kconfig | 1 -
arch/ia64/kernel/crash.c | 2 +-
arch/mips/Kconfig | 8 ++----
arch/mips/include/asm/elf.h | 56 +++++++++++++-----------------------
arch/mips/include/asm/elfcore-compat.h | 29 +++++++++++++++++++
arch/mips/kernel/Makefile | 4 +--
arch/mips/kernel/binfmt_elfn32.c | 106 --------------------------------------------------------------------
arch/mips/kernel/binfmt_elfo32.c | 109 ----------------------------------------------------------------------
arch/mips/kernel/scall64-n64.S | 2 +-
arch/parisc/Kconfig | 1 -
arch/powerpc/Kconfig | 1 -
arch/powerpc/platforms/powernv/opal-core.c | 6 ++--
arch/s390/Kconfig | 1 -
arch/s390/kernel/crash_dump.c | 2 +-
arch/sparc/Kconfig | 1 -
arch/x86/Kconfig | 2 +-
arch/x86/include/asm/compat.h | 11 -------
arch/x86/include/asm/elf.h | 2 +-
arch/x86/include/asm/elfcore-compat.h | 31 ++++++++++++++++++++
fs/Kconfig.binfmt | 2 +-
fs/binfmt_elf.c | 19 ++++++-------
fs/binfmt_elf_fdpic.c | 22 ++++----------
fs/compat_binfmt_elf.c | 7 +----
include/linux/elfcore-compat.h | 15 ++++++++--
include/linux/elfcore.h | 7 ++++-
kernel/kexec_core.c | 2 +-
28 files changed, 128 insertions(+), 324 deletions(-)
create mode 100644 arch/mips/include/asm/elfcore-compat.h
delete mode 100644 arch/mips/kernel/binfmt_elfn32.c
delete mode 100644 arch/mips/kernel/binfmt_elfo32.c
create mode 100644 arch/x86/include/asm/elfcore-compat.h
next prev parent reply other threads:[~2021-01-06 0:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 12:16 in_compat_syscall() on x86 David Laight
2021-01-04 16:46 ` David Laight
2021-01-04 16:58 ` Al Viro
2021-01-04 20:41 ` Eric W. Biederman
2021-01-04 22:34 ` David Laight
2021-01-04 23:04 ` Andy Lutomirski
2021-01-05 0:47 ` Eric W. Biederman
2021-01-05 0:57 ` Al Viro
2021-01-06 0:03 ` Eric W. Biederman
2021-01-06 0:11 ` Bernd Petrovitsch
2021-01-06 0:30 ` Al Viro [this message]
2021-01-05 9:53 ` David Laight
2021-01-05 17:35 ` Andy Lutomirski
2021-01-06 9:42 ` David Laight
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=20210106003016.GZ3579531@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=David.Laight@aculab.com \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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