[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb450443-07c3-438c-888f-30540935da15@intel.com>
Date: Wed, 1 Oct 2025 14:18:57 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Brendan Jackman <jackmanb@...gle.com>, Andy Lutomirski <luto@...nel.org>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
"Liam R. Howlett" <Liam.Howlett@...cle.com>,
Suren Baghdasaryan <surenb@...gle.com>, Michal Hocko <mhocko@...e.com>,
Johannes Weiner <hannes@...xchg.org>, Zi Yan <ziy@...dia.com>,
Axel Rasmussen <axelrasmussen@...gle.com>, Yuanchu Xie <yuanchu@...gle.com>,
Roman Gushchin <roman.gushchin@...ux.dev>
Cc: peterz@...radead.org, bp@...en8.de, dave.hansen@...ux.intel.com,
mingo@...hat.com, tglx@...utronix.de, akpm@...ux-foundation.org,
david@...hat.com, derkling@...gle.com, junaids@...gle.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, reijiw@...gle.com,
rientjes@...gle.com, rppt@...nel.org, vbabka@...e.cz, x86@...nel.org,
yosry.ahmed@...ux.dev
Subject: Re: [PATCH 06/21] mm/page_alloc: add __GFP_SENSITIVE and always set
it
On 9/24/25 07:59, Brendan Jackman wrote:
> +#ifdef CONFIG_MITIGATION_ADDRESS_SPACE_ISOLATION
> +#define ___GFP_SENSITIVE BIT(___GFP_SENSITIVE_BIT)
> +#else
> +#define ___GFP_SENSITIVE 0
> +#endif
This is clearly one of the inflection points of the series.
To go any farther with this approach, I think it's critical to get a few
acks on this hunk specifically. Well, maybe not formal acked-by's, but
at least _clear_ agreement from at least one of:
MEMORY MANAGEMENT - PAGE ALLOCATOR
M: Andrew Morton <akpm@...ux-foundation.org>
M: Vlastimil Babka <vbabka@...e.cz>
... or this approach is dead in the water.
Powered by blists - more mailing lists