On 6/4/26 03:46, Xie Yuanbin wrote: > On Wed, 3 Jun 2026 21:13:30 +0200, David Hildenbrand (Arm) wrote: >> Would the following be sufficient to avoid a full revert and the dependency >> on CONFIG_RAS? >> >> diff --git a/include/trace/events/memory-failure.h >> b/include/trace/events/memory-failure.h >> index aa57cc8f896b..c46b17602578 100644 >> --- a/include/trace/events/memory-failure.h >> +++ b/include/trace/events/memory-failure.h >> @@ -1,6 +1,7 @@ >> /* SPDX-License-Identifier: GPL-2.0 */ >> #undef TRACE_SYSTEM >> -#define TRACE_SYSTEM memory_failure >> +/* Some user space relies on ras/memory_failure_event */ >> +#define TRACE_SYSTEM ras >> #define TRACE_INCLUDE_FILE memory-failure >> >> #if !defined(_TRACE_MEMORY_FAILURE_H) || defined(TRACE_HEADER_MULTI_READ) > > Yes, it should be. In fact, when I sent the V2 patch, I had already > considered this issue, and that's exactly what I did: > Link: https://lore.kernel.org/[email protected] > > However, David Hildenbrand advised me at that time to completely > remove the dependence on RAS: > Link: https://lore.kernel.org/[email protected]
Yeah, if only I had known that we would break user space by changing trace events ... now we know :) Do you have capacity to send a fix? -- Cheers, David
