[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <59d518698f664e07c036a5098833d7b56b953305.camel@intel.com>
Date: Fri, 21 Jun 2024 22:06:38 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "peterx@...hat.com" <peterx@...hat.com>
CC: "hughd@...gle.com" <hughd@...gle.com>, "willy@...radead.org"
<willy@...radead.org>, "Hansen, Dave" <dave.hansen@...el.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>, "vbabka@...e.cz"
<vbabka@...e.cz>, "riel@...riel.com" <riel@...riel.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>, "kirill@...temov.name"
<kirill@...temov.name>, "christophe.leroy@...roup.eu"
<christophe.leroy@...roup.eu>, "aneesh.kumar@...ux.ibm.com"
<aneesh.kumar@...ux.ibm.com>, "Jiang, Dave" <dave.jiang@...el.com>,
"tglx@...utronix.de" <tglx@...utronix.de>, "mpe@...erman.id.au"
<mpe@...erman.id.au>, "npiggin@...il.com" <npiggin@...il.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>, "osalvador@...e.de"
<osalvador@...e.de>, "linuxppc-dev@...ts.ozlabs.org"
<linuxppc-dev@...ts.ozlabs.org>, "bp@...en8.de" <bp@...en8.de>,
"mgorman@...hsingularity.net" <mgorman@...hsingularity.net>, "Huang, Ying"
<ying.huang@...el.com>, "x86@...nel.org" <x86@...nel.org>, "Williams, Dan J"
<dan.j.williams@...el.com>
Subject: Re: [PATCH 6/7] mm/x86: Add missing pud helpers
On Fri, 2024-06-21 at 16:27 -0400, Peter Xu wrote:
> On Fri, Jun 21, 2024 at 07:36:30PM +0000, Edgecombe, Rick P wrote:
> > On Fri, 2024-06-21 at 07:51 -0700, Dave Hansen wrote:
> > >
> > > But, still, what if you take a Dirty=1,Write=1 pud and pud_modify() it
> > > to make it Dirty=1,Write=0? What prevents that from being
> > > misinterpreted by the hardware as being a valid 1G shadow stack mapping?
> >
> > Hmm, it looks like we could use an arch_check_zapped_pud() that does a
> > warning
> > like arch_check_zapped_pte/pmd() too. Not that we had no use for one before
> > this.
>
> I can definitely look into that, but this check only happens when zapping,
> and IIUC it means there can still be outliers floating around. I wonder
> whether it should rely on page_table_check_pxx_set() from that regard.
Yes, it's not perfect. Hmm, it looks like the page_table_check would catch a lot
more cases, but it would have to be changed to plumb the vma in.
Powered by blists - more mailing lists