On Mon, Jun 01, 2020 at 12:17:27PM -0300, Luis Machado wrote: > On 6/1/20 9:07 AM, Catalin Marinas wrote: > > On Fri, May 29, 2020 at 06:25:14PM -0300, Luis Machado wrote: > > > I have a question about siginfo MTE information. I suppose SEGV_MTESERR will > > > be the most useful setting for debugging, right? Does si_addr contain the > > > tagged pointer with the logical tag, a zero-tagged memory address or a > > > tagged pointer with the allocation tag? > > > > The si_addr is zero-tagged currently. We were planning to expose the tag > > in FAR_EL1 as a separate siginfo field. See these discussions: > > > > https://lore.kernel.org/linux-arm-kernel/20200513180914.50892-1-pcc@xxxxxxxxxx/ > > https://lore.kernel.org/linux-arm-kernel/20200521022943.195898-1-pcc@xxxxxxxxxx/ > > > > In theory, we could add the tag to si_addr for SEGV_MTESERR, it > > shouldn't break the existing ABI (well, it depends on how you look at > > it). > > Having additional fields in siginfo that hold useful information is probably > best for debuggers. See my comment below about Intel MPX. > > > > From the debugger user's perspective, one would want to see both the logical > > > tag and the allocation tag. And it would be handy to have both available in > > > siginfo. Does that make sense? > > > > The debugger can access the allocation tag via PTRACE_PEEKMTETAGS. I > > don't think the kernel should provide this in siginfo. Also, the signal > > handler can do an LDG and read the allocation tag directly, no need for > > it to be in siginfo. > > While the debugger can request this information from the kernel, the > debugger has already received a SIGSEGV signal and will have to fetch > siginfo for si_code. Having to do another PTRACE_PEEKMTETAGS call just to > fetch the allocation tag doesn't sound great. Remember this can travel > through TCP to gdbserver so it can call ptrace from the remote's end. It > would be best to avoid the round trip. But given that this is supposed to be a rare event, does another round trip to read some memory matter much? > Also, there seems to be past precedent to include more information in > siginfo. For example, Intel MPX includes upper/lower bounds violation data > in there. There is a possible race here with getting the allocation tag. For example, another thread of the same process unmaps the memory and reading the tag from the user memory is no longer possible. If we are to add such information, we can't guarantee it's always possible (it may differ from the MPX case). In general, I don't like providing information that's already accessible by other means (unless there's a performance issue but I don't think that's the case here). > Regarding using LDG, are you suggesting force-running this particular > instruction in the traced process? If so, that isn't the way GDB (in > particular, not sure about LLDB) does things. No. What I meant is that if the signal handler itself needs the information, it can execute an LDG. For gdb, the equivalent currently is PTRACE_PEEKMTETAGS. > > > Also, when would we see SEGV_MTEAERR, for example? That would provide no > > > additional information about a particular memory address, which is not that > > > useful for the debugger. > > > > Yeah, we can't really do much here since the hardware doesn't provide us > > such information. The async mode is only useful as a general test to see > > if your program has MTE faults but for actual debugging you'd have to > > switch to synchronous. For glibc at least, I think the mode can be > > driven by an environment variable. > > I suspect SEGV_MTESERR would be a reasonable default then, for whoever is > responsible for setting the default settings. > > I'm assuming it is not the debugger, as it doesn't know how to toggle prctl > settings. The debugger could set the environment before starting the debugged process. But yes, that would be the C library. -- Catalin
