Peter Collingbourne <pcc@xxxxxxxxxx> writes: > 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, create a new pair of > fields in siginfo._sigfault, and store the tag bits of FAR_EL1 there, > together with a mask specifying which bits are valid. > > A flag is added to si_faultflags to allow userspace to determine whether > the values in the fields are valid. I think I am missing some things: Today it is documented that the tag bits are cleared, and so we can't use the highbits to hold the tag bits by default. Why do you need to deliver which tag bits are valid? That feels like an implementation detail that is needed to setup the tag bits. It feels like it would be constant per process. So I don't understand why the siginfo needs to report information the process should already have. Want prevents adding a sigaction sa_flag SA_EXPOSE_TABITS that when set causes the high bits to be set, and when clear (the default) will have the signal delivery code clear those bits. That should be enough for code that wants the tag bits to ask for them. As userspace would need to be updated to get the new bits Even if you have chained handlers. The chaining mechanism would need to be updated and it could call the aware handlers first then clear the tag bits and call the rest of the handlers. It feels like always passing the tag bits in the address and then clearing them in the copy to userspace if the signal handler is not ready for them would be easier to maintain. Eric
