aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/arm64
diff options
context:
space:
mode:
authorPeter Collingbourne <pcc@google.com>2020-11-20 12:33:45 -0800
committerEric W. Biederman <ebiederm@xmission.com>2020-11-23 10:31:06 -0600
commit6ac05e832a9e96f9b1c42a8917cdd317d7b6c8fa (patch)
tree72e13727569f07efa33909831e2de1e7e9743bef /Documentation/arm64
parentsignal: define the SA_UNSUPPORTED bit in sa_flags (diff)
downloadlinux-dev-6ac05e832a9e96f9b1c42a8917cdd317d7b6c8fa.tar.xz
linux-dev-6ac05e832a9e96f9b1c42a8917cdd317d7b6c8fa.zip
signal: define the SA_EXPOSE_TAGBITS bit in sa_flags
Architectures that support address tagging, such as arm64, may want to expose fault address tag bits to the signal handler to help diagnose memory errors. However, these bits have not been previously set, and their presence may confuse unaware user applications. Therefore, introduce a SA_EXPOSE_TAGBITS flag bit in sa_flags that a signal handler may use to explicitly request that the bits are set. The generic signal handler APIs expect to receive tagged addresses. Architectures may specify how to untag addresses in the case where SA_EXPOSE_TAGBITS is clear by defining the arch_untagged_si_addr function. Signed-off-by: Peter Collingbourne <pcc@google.com> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com> Link: https://linux-review.googlesource.com/id/I16dd0ed2081f091fce97be0190cb8caa874c26cb Link: https://lkml.kernel.org/r/13cf24d00ebdd8e1f55caf1821c7c29d54100191.1605904350.git.pcc@google.com Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Diffstat (limited to 'Documentation/arm64')
0 files changed, 0 insertions, 0 deletions