public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
	Michael Schmitz <schmitzmic@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Arnd Bergmann <arnd@arndb.de>, Cyril Hrubis <chrubis@suse.cz>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] exit cleanups for v5.15-rc1
Date: Tue, 31 Aug 2021 12:25:24 -0500	[thread overview]
Message-ID: <87bl5d7chn.fsf@disp2133> (raw)


Please pull the exit-cleanups-for-v5.15 branch from the git tree:

  git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git exit-cleanups-for-v5.15

  HEAD: d21918e5a94a862ccb297b9f2be38574c865fda0 signal/seccomp: Dump core when there is only one live thread

In preparation of doing something about PTRACE_EVENT_EXIT I have started
cleaning up various pieces of code related to do_exit.  Most of that
code I did not manage to get tested and reviewed before the merge window
opened but a handful of very useful cleanups are ready to be merged.

The first change is simply the removal of the bdflush system call.  The
code has now been disabled long enough that even the oldest userspace
working userspace setups anyone can find to test are fine with the
bdflush system call being removed.

Changing m68k fsp040_die to use force_sigsegv(SIGSEGV) instead of
calling do_exit directly is interesting only in that it is nearly the
most difficult of the incorrect uses of do_exit to remove.

The change to the seccomp code to simply send a signal instead of
calling do_coredump directly is a very nice little cleanup made possible
by realizing the existing signal sending helpers were missing a little
bit of functionality that is easy to provide.

Eric W. Biederman (4):
      exit/bdflush: Remove the deprecated bdflush system call
      signal/m68k: Use force_sigsegv(SIGSEGV) in fpsp040_die
      signal/seccomp: Refactor seccomp signal and coredump generation
      signal/seccomp: Dump core when there is only one live thread

 arch/alpha/kernel/syscalls/syscall.tbl             |  2 +-
 arch/arm/tools/syscall.tbl                         |  2 +-
 arch/arm64/include/asm/unistd32.h                  |  2 +-
 arch/ia64/kernel/syscalls/syscall.tbl              |  2 +-
 arch/m68k/fpsp040/skeleton.S                       |  3 +-
 arch/m68k/kernel/syscalls/syscall.tbl              |  2 +-
 arch/m68k/kernel/traps.c                           |  2 +-
 arch/microblaze/kernel/syscalls/syscall.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/sh/kernel/syscalls/syscall.tbl                |  2 +-
 arch/sparc/kernel/syscalls/syscall.tbl             |  2 +-
 arch/x86/entry/syscalls/syscall_32.tbl             |  2 +-
 arch/xtensa/kernel/syscalls/syscall.tbl            |  2 +-
 fs/buffer.c                                        | 27 --------------
 include/linux/sched/signal.h                       |  1 +
 include/linux/syscalls.h                           |  1 -
 include/uapi/linux/capability.h                    |  1 -
 kernel/seccomp.c                                   | 42 ++++------------------
 kernel/signal.c                                    | 30 +++++++++++++---
 kernel/sys_ni.c                                    |  1 -
 tools/perf/arch/powerpc/entry/syscalls/syscall.tbl |  2 +-
 tools/perf/arch/s390/entry/syscalls/syscall.tbl    |  2 +-
 25 files changed, 53 insertions(+), 87 deletions(-)

Eric

             reply	other threads:[~2021-08-31 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 17:25 Eric W. Biederman [this message]
2021-08-31 18:55 ` [GIT PULL] exit cleanups for v5.15-rc1 Eric W. Biederman
2021-09-01 22:44 ` 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=87bl5d7chn.fsf@disp2133 \
    --to=ebiederm@xmission.com \
    --cc=arnd@arndb.de \
    --cc=chrubis@suse.cz \
    --cc=geert@linux-m68k.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schmitzmic@gmail.com \
    --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