RE: mm/memory-failure tracepoint change breaks userspace rasdaemon

[Zhuo, Qiuxu]

> From: David Hildenbrand (Arm) <david@xxxxxxxxxx>
> [...]
> 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
> 

Thanks all for the discussion on this issue.

We applied David's above fix to v7.1-rc3, tested it, and confirmed that rasdaemon 
can again enable and receive the memory_failure event.

   Rasdaemon logs:
     ...
     rasdaemon: ras:memory_failure_event event enabled
     rasdaemon: Enabled event ras:memory_failure_event
    ...
    <...>-2513  [000] .....     0.000021 memory_failure_event [ALERT] 2026-06-04 23:30:43 +0800 pfn=0x144e6f page_type=dirty LRU page action_result=Recovered
    ...

-Qiuxu