From: Peter Collingbourne <pcc@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Evgenii Stepanov <eugenis@google.com>,
Kostya Serebryany <kcc@google.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Dave Martin <Dave.Martin@arm.com>, Will Deacon <will@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>
Cc: Andrey Konovalov <andreyknvl@google.com>,
Helge Deller <deller@gmx.de>,
Kevin Brodsky <kevin.brodsky@arm.com>,
linux-api@vger.kernel.org,
David Spickett <david.spickett@linaro.org>,
Peter Collingbourne <pcc@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v16 0/6] arm64: expose FAR_EL1 tag bits in siginfo
Date: Thu, 12 Nov 2020 18:53:30 -0800 [thread overview]
Message-ID: <cover.1605235762.git.pcc@google.com> (raw)
The kernel currently clears the tag bits (i.e. bits 56-63) in the fault
address exposed via siginfo.si_addr and sigcontext.fault_address. However,
the tag bits may be needed by tools in order to accurately diagnose
memory errors, such as HWASan [1] or future tools based on the Memory
Tagging Extension (MTE).
We should not stop clearing these bits in the existing fault address
fields, because there may be existing userspace applications that are
expecting the tag bits to be cleared. Instead, introduce a flag in
sigaction.sa_flags, SA_EXPOSE_TAGBITS, and only expose the tag bits
there if the signal handler has this flag set.
In order to allow userspace to determine whether SA_EXPOSE_TAGBITS
is supported, we first introduce a mechanism for userspace to detect
kernel support for SA_* flags.
The series can be viewed on Gerrit here:
https://linux-review.googlesource.com/id/Ia8876bad8c798e0a32df7c2ce1256c4771c81446
[1] http://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html
Helge Deller (1):
parisc: Drop parisc special case for __sighandler_t
Peter Collingbourne (5):
parisc: start using signal-defs.h
arch: move SA_* definitions to generic headers
signal: clear non-uapi flag bits when passing/returning sa_flags
signal: define the SA_UNSUPPORTED bit in sa_flags
arm64: expose FAR_EL1 tag bits in siginfo
Documentation/arm64/tagged-pointers.rst | 25 ++++++---
arch/alpha/include/uapi/asm/signal.h | 14 -----
arch/arm/include/asm/signal.h | 2 +
arch/arm/include/uapi/asm/signal.h | 27 ++--------
arch/arm64/include/asm/exception.h | 2 +-
arch/arm64/include/asm/signal.h | 25 +++++++++
arch/arm64/include/asm/system_misc.h | 2 +-
arch/arm64/include/asm/traps.h | 6 +--
arch/arm64/kernel/debug-monitors.c | 5 +-
arch/arm64/kernel/entry-common.c | 2 -
arch/arm64/kernel/ptrace.c | 7 +--
arch/arm64/kernel/sys_compat.c | 5 +-
arch/arm64/kernel/traps.c | 29 ++++++-----
arch/arm64/mm/fault.c | 68 ++++++++++++++-----------
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/asm/signal.h | 2 +
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 | 57 +++++++++++++++++++++
include/uapi/asm-generic/signal.h | 29 -----------
kernel/signal.c | 39 +++++++++++---
31 files changed, 231 insertions(+), 366 deletions(-)
create mode 100644 arch/arm64/include/asm/signal.h
--
2.29.2.299.gdc1121823c-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-11-13 2:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 2:53 Peter Collingbourne [this message]
2020-11-13 2:53 ` [PATCH v16 1/6] parisc: Drop parisc special case for __sighandler_t Peter Collingbourne
2020-11-13 2:53 ` [PATCH v16 2/6] parisc: start using signal-defs.h Peter Collingbourne
2020-11-13 2:53 ` [PATCH v16 3/6] arch: move SA_* definitions to generic headers Peter Collingbourne
2020-11-13 2:53 ` [PATCH v16 4/6] signal: clear non-uapi flag bits when passing/returning sa_flags Peter Collingbourne
2020-11-13 2:53 ` [PATCH v16 5/6] signal: define the SA_UNSUPPORTED bit in sa_flags Peter Collingbourne
2020-11-14 13:53 ` Eric W. Biederman
2020-11-14 22:12 ` Peter Collingbourne
2020-11-16 23:48 ` Eric W. Biederman
2020-11-13 2:53 ` [PATCH v16 6/6] arm64: expose FAR_EL1 tag bits in siginfo Peter Collingbourne
2020-11-15 14:08 ` Eric W. Biederman
2020-11-16 13:36 ` Dave Martin
2020-11-16 18:32 ` Peter Collingbourne
2020-11-16 19:01 ` Catalin Marinas
2020-11-16 21:55 ` Eric W. Biederman
2020-11-16 22:08 ` Catalin Marinas
2020-11-16 23:28 ` Peter Collingbourne
2020-11-16 23:59 ` Eric W. Biederman
2020-11-17 3:24 ` Peter Collingbourne
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=cover.1605235762.git.pcc@google.com \
--to=pcc@google.com \
--cc=Dave.Martin@arm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andreyknvl@google.com \
--cc=catalin.marinas@arm.com \
--cc=david.spickett@linaro.org \
--cc=deller@gmx.de \
--cc=ebiederm@xmission.com \
--cc=eugenis@google.com \
--cc=kcc@google.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oleg@redhat.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).