[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <797a2b64ed0949b6905b3c3e8f049a23@intel.com>
Date: Mon, 18 Jul 2022 19:22:24 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: "Williams, Dan J" <dan.j.williams@...el.com>,
"chu, jane" <jane.chu@...cle.com>, "bp@...en8.de" <bp@...en8.de>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hch@....de" <hch@....de>,
"nvdimm@...ts.linux.dev" <nvdimm@...ts.linux.dev>
Subject: RE: [PATCH v3] x86/mce: retrieve poison range from hardware
> It appears the kernel is trusting that ->physical_addr_mask is non-zero
> in other paths. So this is at least equally broken in the presence of a
> broken BIOS. The impact is potentially larger though with this change,
> so it might be a good follow-on patch to make sure that
> ->physical_addr_mask gets fixed up to a minimum mask value.
Agreed. Separate patch to sanitize early, so other kernel code can just use it.
-Tony
Powered by blists - more mailing lists