linux-kernel - Re: [PATCH] mm/page_alloc: only set ALLOC_HIGHATOMIC for __GPF

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: <5e3bd766-0845-4d7a-acf3-1493eb925451@suse.cz>
Date: Fri, 29 Aug 2025 11:30:17 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: Sergey Senozhatsky <senozhatsky@...omium.org>,
 Andrew Morton <akpm@...ux-foundation.org>,
 Thadeu Lima de Souza Cascardo <cascardo@...lia.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
 Suren Baghdasaryan <surenb@...gle.com>, Michal Hocko <mhocko@...e.com>,
 Brendan Jackman <jackmanb@...gle.com>, Johannes Weiner <hannes@...xchg.org>,
 Zi Yan <ziy@...dia.com>, Mel Gorman <mgorman@...hsingularity.net>,
 kernel-dev@...lia.com, Helen Koike <koike@...lia.com>,
 Matthew Wilcox <willy@...radead.org>,
 Thierry Reding <thierry.reding@...il.com>, neil@...wn.name
Subject: Re: [PATCH] mm/page_alloc: only set ALLOC_HIGHATOMIC for __GPF_HIGH
 allocations

On 8/29/25 10:56, Sergey Senozhatsky wrote:
> On (25/08/29 10:38), Vlastimil Babka wrote:
>> On 8/29/25 10:36, Vlastimil Babka wrote:
>> > On 8/14/25 19:22, Thadeu Lima de Souza Cascardo wrote:
> [..]
>> > Agreed with others that this change matches the original intention and it
>> > must have been an oversight. Also found nothing to the contrary in the
>> > original threads.
>> 
>> Oops, forgot to add
>> 
>> Reviewed-by: Vlastimil Babka <vbabka@...e.cz>
> 
> Thank you!
> 
> FWIW
> Tested-by: Sergey Senozhatsky <senozhatsky@...omium.org>
> 
> This needs Cc: stable@...r.kernel.org  all the way down to 5.15,
> as far as I can tell.

If that problem bothers users of LTS kernels in that range, we can do that.
I wonder a bit how it was only found out now as a regression in the
browser/desktop environment test if it's that old? Is there another factor
i.e. some new frequesnt source of allocations that trigger it?