linux-kernel - Re: [PATCH v3] mm/memory-failure: remove the selection of RAS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fc7bae22-0705-475a-be89-8bb3ca12384d@kernel.org>
Date: Thu, 20 Nov 2025 14:59:54 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Xie Yuanbin <xieyuanbin1@...wei.com>, tony.luck@...el.com, bp@...en8.de,
 linmiaohe@...wei.com, nao.horiguchi@...il.com, rostedt@...dmis.org,
 mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
 akpm@...ux-foundation.org, lorenzo.stoakes@...cle.com,
 Liam.Howlett@...cle.com, vbabka@...e.cz, rppt@...nel.org, surenb@...gle.com,
 mhocko@...e.com
Cc: linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
 linux-mm@...ck.org, linux-trace-kernel@...r.kernel.org, will@...nel.org,
 liaohua4@...wei.com, lilinjie8@...wei.com
Subject: Re: [PATCH v3] mm/memory-failure: remove the selection of RAS

On 11/19/25 10:59, Xie Yuanbin wrote:
> The commit 97f0b13452198290799f ("tracing: add trace event for
> memory-failure") introduces the selection of RAS in memory-failure.
> This commit is just a tracing feature; in reality, there is no dependency
> between memory-failure and RAS. RAS increases the size of the bzImage
> image by 8k, which is very valuable for embedded devices.
> 
> Move the memory-failure traceing code from ras_event.h to
> memory-failure.h and remove the selection of RAS.
> 
> v2->v3: https://lore.kernel.org/20251104072306.100738-3-xieyuanbin1@huawei.com
>    - Change define TRACE_SYSTEM from ras to memory_failure
>    - Add include/trace/events/memory-failure.h to
>      "HWPOISON MEMORY FAILURE HANDLING" section in MAINTAINERS
>    - Rebase to latest linux-next source
> 
> v1->v2: https://lore.kernel.org/20251103033536.52234-2-xieyuanbin1@huawei.com
>    - Move the memory-failure traceing code from ras_event.h to
>      memory-failure.h
> 
> Signed-off-by: Xie Yuanbin <xieyuanbin1@...wei.com>
> Cc: David Hildenbrand (Red Hat) <david@...nel.org>
> Cc: Borislav Petkov <bp@...en8.de>
> Cc: Miaohe Lin <linmiaohe@...wei.com>
> ---
>   MAINTAINERS                           |  1 +
>   include/ras/ras_event.h               | 87 ------------------------
>   include/trace/events/memory-failure.h | 98 +++++++++++++++++++++++++++
>   mm/Kconfig                            |  1 -
>   mm/memory-failure.c                   |  5 +-
>   5 files changed, 103 insertions(+), 89 deletions(-)
>   create mode 100644 include/trace/events/memory-failure.h
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7310d9ca0370..43d6eb95fb05 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11631,10 +11631,11 @@ R:	Naoya Horiguchi <nao.horiguchi@...il.com>
>   L:	linux-mm@...ck.org
>   S:	Maintained
>   F:	include/linux/memory-failure.h
>   F:	mm/hwpoison-inject.c
>   F:	mm/memory-failure.c
> +F:	include/trace/events/memory-failure.

These are ordered alphabetically, so it should be further up next to the 
other include.

With that

Acked-by: David Hildenbrand (Red Hat) <david@...nel.org>

-- 
Cheers

David