linux-kernel - RE: [PATCH v2] ACPI: APEI: EINJ: EINJV2 support added

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: <SJ1PR11MB6083A266C4A869FC9AAA5A9AFC6D9@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date:   Thu, 4 May 2023 16:43:53 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Piyush Malgujar <pmalgujar@...vell.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
        "Williams, Dan J" <dan.j.williams@...el.com>,
        "xueshuai@...ux.alibaba.com" <xueshuai@...ux.alibaba.com>,
        "jaylu102@....com" <jaylu102@....com>,
        "benjamin.cheatham@....com" <benjamin.cheatham@....com>,
        "bp@...en8.de" <bp@...en8.de>,
        "james.morse@....com" <james.morse@....com>,
        "lenb@...nel.org" <lenb@...nel.org>,
        "rafael@...nel.org" <rafael@...nel.org>
CC:     "jannadurai@...vell.com" <jannadurai@...vell.com>,
        "cchavva@...vell.com" <cchavva@...vell.com>
Subject: RE: [PATCH v2] ACPI: APEI: EINJ: EINJV2 support added

+An error injection example::
+
+  # cd /sys/kernel/debug/apei/einj
+  # cat available_error_type		# See which errors can be injected
+  0x00000001	EINJV2 Processor Error
+  0x00000002	EINJV2 Memory Error
+  0x00000004	EINJV2 PCI Express Error
+  # echo 0x2 > error_type
+  # echo 0x5 > flags
+  # echo 0x12345000 > param1
+  # echo 0x2 > param5
+  # echo 1 > error_inject

Is the expectation that platforms that implement EINJV2 will not include legacy
EINJ support?

The Linux error injection API is all in "debugfs", so maybe there shouldn't be
an expectation that old injection tests will work on new systems. But this is
going to catch some by surprise.

Maybe it would be better to change the top-level directory to:

	/sys/kernel/debug/apei/einjv2

so that old scripts and programs will fail immediately, rather than do
weird things writing legacy einj values to the various files.

And ... since there is no expectation of backward compatibility ... perhaps
take this opportunity to re-think the entire API? Perhaps something like this,
With just a single file for all parameters?

# echo "memory notrigger 0x12345 0x2" > /sys/kernel/debug/apei/einjv2/inject

or separate files for each injection target:

# echo "0x12345 0x2 notrigger" > /sys/kernel/debug/apei/einjv2/inject_memory

-Tony