[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60836FCA1B8B317003CBF99FFC559@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Tue, 27 Sep 2022 20:34:44 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Tai, Thomas" <thomas.tai@...cle.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"jarkko@...nel.org" <jarkko@...nel.org>,
"reinette.chatre@...el.co" <reinette.chatre@...el.co>,
"naoya.horiguchi@....com" <naoya.horiguchi@....com>,
"linmiaohe@...wei.com" <linmiaohe@...wei.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Tai, Thomas" <thomas.tai@...cle.com>
Subject: RE: [PATCH] x86/sgx: Add code to inject hwpoison into SGX memory
> Inspired by commit c6acb1e7bf46 (x86/sgx: Add hook to error injection
> address validation), add a similar code in hwpoison_inject function to
> check if the address is located in SGX Memory. The error will then be
> handled by the arch_memory_failure function in the SGX driver.
Looks good to me.
[I wish that Linux hadn't called this "hwpoison_inject()" because there's nothing
hardware related about this injection. But you are just an innocent consumer of
that poor naming choice]
Reviewed-by: Tony Luck <tony.luck@...el.com>
-Tony
Powered by blists - more mailing lists