From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] signal enhancements for v5.11-rc1
Date: Tue, 15 Dec 2020 16:43:41 -0600 [thread overview]
Message-ID: <87bleubsgy.fsf@x220.int.ebiederm.org> (raw)
Please pull the signal-for-v5.11 branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git signal-for-v5.11
HEAD: bc54a5cda97917155b8da0d99afe1dc0ed0b30db signal/parisc: Remove parisc specific definition of __ARCH_UAPI_SA_FLAGS
This is the work from Peter Collingbourne to add an new signal action
flag SA_EXPOSE_TAGBITS on arm64. There was a lot of discussion leading
up to this and ultimately we were able to channel the original proposal
into something that is much more maintainable than an arm64 specific
hack.
Most of this I believe has already come in through Catalin Marinas pull
request "arm64 updates for 5.11". As I took the generic bits of the
cleanup and place it in a non-rebasing branch. There is a compile fix
for parisc that was caught late that I don't believe Catalin picked up.
The generic changes are mostly about removing never used HP-UX
compatibility from parisc headers and consolidating the SA_* flags
definitions into a generic header as much as possible. We only have 32
SA_* flag bits total, so we need to be careful. But as this is the
first addition in a decade or so I think we are fine for the forseeable
future.
Eric W. Biederman (1):
signal/parisc: Remove parisc specific definition of __ARCH_UAPI_SA_FLAGS
Helge Deller (1):
parisc: Drop parisc special case for __sighandler_t
Peter Collingbourne (6):
parisc: start using signal-defs.h
arch: move SA_* definitions to generic headers
signal: clear non-uapi flag bits when passing/returning sa_flags
arch: provide better documentation for the arch-specific SA_* flags
signal: define the SA_UNSUPPORTED bit in sa_flags
signal: define the SA_EXPOSE_TAGBITS bit in sa_flags
arch/alpha/include/uapi/asm/signal.h | 14 --------
arch/arm/include/asm/signal.h | 2 ++
arch/arm/include/uapi/asm/signal.h | 27 ++-------------
arch/h8300/include/uapi/asm/signal.h | 24 -------------
arch/ia64/include/uapi/asm/signal.h | 24 -------------
arch/m68k/include/uapi/asm/signal.h | 24 -------------
arch/mips/include/uapi/asm/signal.h | 12 -------
arch/parisc/include/uapi/asm/signal.h | 34 +-----------------
arch/powerpc/include/uapi/asm/signal.h | 24 -------------
arch/s390/include/uapi/asm/signal.h | 24 -------------
arch/sparc/include/uapi/asm/signal.h | 4 +--
arch/x86/include/uapi/asm/signal.h | 24 -------------
arch/x86/kernel/signal_compat.c | 7 ----
arch/xtensa/include/uapi/asm/signal.h | 24 -------------
include/linux/signal.h | 14 ++++++++
include/linux/signal_types.h | 12 +++++++
include/uapi/asm-generic/signal-defs.h | 63 ++++++++++++++++++++++++++++++++++
include/uapi/asm-generic/signal.h | 29 ----------------
kernel/signal.c | 40 +++++++++++++++++++++
19 files changed, 136 insertions(+), 290 deletions(-)
Eric
next reply other threads:[~2020-12-15 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 22:43 Eric W. Biederman [this message]
2020-12-16 3:17 ` Linus Torvalds
2020-12-16 3: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=87bleubsgy.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--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
Powered by JetHome