From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: 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>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Andrey Konovalov <andreyknvl@google.com>,
linux-api@vger.kernel.org, Helge Deller <deller@gmx.de>,
David Spickett <david.spickett@linaro.org>
Subject: Re: [PATCH v21 2/2] arm64: expose FAR_EL1 tag bits in siginfo
Date: Mon, 23 Nov 2020 18:56:20 +0000 [thread overview]
Message-ID: <20201123185620.GD2438@gaia> (raw)
In-Reply-To: <0010296597784267472fa13b39f8238d87a72cf8.1605904350.git.pcc@google.com>
On Fri, Nov 20, 2020 at 12:33:46PM -0800, Peter Collingbourne wrote:
> 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).
>
> Expose these bits via the arch_untagged_si_addr mechanism, so that
> they are only exposed to signal handlers with the SA_EXPOSE_TAGBITS
> flag set.
>
> [1] http://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html
>
> Signed-off-by: Peter Collingbourne <pcc@google.com>
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> Link: https://linux-review.googlesource.com/id/Ia8876bad8c798e0a32df7c2ce1256c4771c81446
Applied to arm64 (for-next/signal-tag-bits), thanks!
[2/2] arm64: expose FAR_EL1 tag bits in siginfo
https://git.kernel.org/arm64/c/dceec3ff7807
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Andrey Konovalov <andreyknvl@google.com>,
Helge Deller <deller@gmx.de>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Oleg Nesterov <oleg@redhat.com>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
Kostya Serebryany <kcc@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-api@vger.kernel.org,
David Spickett <david.spickett@linaro.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>, Dave Martin <Dave.Martin@arm.com>,
Evgenii Stepanov <eugenis@google.com>
Subject: Re: [PATCH v21 2/2] arm64: expose FAR_EL1 tag bits in siginfo
Date: Mon, 23 Nov 2020 18:56:20 +0000 [thread overview]
Message-ID: <20201123185620.GD2438@gaia> (raw)
In-Reply-To: <0010296597784267472fa13b39f8238d87a72cf8.1605904350.git.pcc@google.com>
On Fri, Nov 20, 2020 at 12:33:46PM -0800, Peter Collingbourne wrote:
> 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).
>
> Expose these bits via the arch_untagged_si_addr mechanism, so that
> they are only exposed to signal handlers with the SA_EXPOSE_TAGBITS
> flag set.
>
> [1] http://clang.llvm.org/docs/HardwareAssistedAddressSanitizerDesign.html
>
> Signed-off-by: Peter Collingbourne <pcc@google.com>
> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> Link: https://linux-review.googlesource.com/id/Ia8876bad8c798e0a32df7c2ce1256c4771c81446
Applied to arm64 (for-next/signal-tag-bits), thanks!
[2/2] arm64: expose FAR_EL1 tag bits in siginfo
https://git.kernel.org/arm64/c/dceec3ff7807
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-23 18:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 20:33 [PATCH v21 1/2] signal: define the SA_EXPOSE_TAGBITS bit in sa_flags Peter Collingbourne
2020-11-20 20:33 ` Peter Collingbourne
2020-11-20 20:33 ` [PATCH v21 2/2] arm64: expose FAR_EL1 tag bits in siginfo Peter Collingbourne
2020-11-20 20:33 ` Peter Collingbourne
2020-11-23 18:56 ` Catalin Marinas [this message]
2020-11-23 18:56 ` Catalin Marinas
2021-01-13 14:51 ` Andrey Konovalov
2021-01-13 14:51 ` Andrey Konovalov
2021-01-13 15:46 ` Catalin Marinas
2021-01-13 15:46 ` Catalin Marinas
2020-11-20 23:22 ` [PATCH v21 1/2] signal: define the SA_EXPOSE_TAGBITS bit in sa_flags Eric W. Biederman
2020-11-20 23:22 ` Eric W. Biederman
2020-11-23 11:49 ` Catalin Marinas
2020-11-23 11:49 ` Catalin Marinas
2020-11-23 15:53 ` Eric W. Biederman
2020-11-23 15:53 ` Eric W. Biederman
2020-11-23 15:59 ` Catalin Marinas
2020-11-23 15:59 ` Catalin Marinas
2020-11-23 16:17 ` Eric W. Biederman
2020-11-23 16:17 ` Eric W. Biederman
2020-11-23 16:23 ` Catalin Marinas
2020-11-23 16:23 ` Catalin Marinas
2020-11-23 17:30 ` Eric W. Biederman
2020-11-23 17:30 ` Eric W. Biederman
2020-11-23 18:53 ` Catalin Marinas
2020-11-23 18:53 ` Catalin Marinas
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=20201123185620.GD2438@gaia \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andreyknvl@google.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=pcc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.