linux-hardening - [PATCH 2/2] pstore/ramoops: Fix ECC parameter help text

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: <20260218193940.912143-3-gpiccoli@igalia.com>
Date: Wed, 18 Feb 2026 16:37:32 -0300
From: "Guilherme G. Piccoli" <gpiccoli@...lia.com>
To: linux-hardening@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
	kees@...nel.org,
	tony.luck@...el.com,
	kernel-dev@...lia.com,
	kernel@...ccoli.net,
	"Guilherme G. Piccoli" <gpiccoli@...lia.com>
Subject: [PATCH 2/2] pstore/ramoops: Fix ECC parameter help text

In order to set ECC on ramoops, the parameter "ecc" should be
used. The variable that carries this information is "ramoops_ecc".
Due to some confusion in the parameter setting functions, modinfo
ends-up showing both "ecc" and "ramoops_ecc" as valid parameters,
but only "ecc" is the valid one, hence this fix to the parameter
help text.

Signed-off-by: Guilherme G. Piccoli <gpiccoli@...lia.com>
---
 fs/pstore/ram.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index 39936d6da0dd..295a837731a0 100644
--- a/fs/pstore/ram.c
+++ b/fs/pstore/ram.c
@@ -71,7 +71,7 @@ MODULE_PARM_DESC(max_reason,
 
 static int ramoops_ecc;
 module_param_named(ecc, ramoops_ecc, int, 0400);
-MODULE_PARM_DESC(ramoops_ecc,
+MODULE_PARM_DESC(ecc,
 		"if non-zero, the option enables ECC support and specifies "
 		"ECC buffer size in bytes (1 is a special value, means 16 "
 		"bytes ECC)");
-- 
2.50.1