linux-kernel - Re: [GIT PULL] MM updates for 6.19-rc1

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] [day] [month] [year] [list]

Message-ID: <CAFr9PX=_HaM3_xPtTiBn5Gw5-0xcRpawpJ02NStfdr0khF2k7g@mail.gmail.com>
Date: Thu, 11 Dec 2025 20:12:18 +0900
From: Daniel Palmer <daniel@...f.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, mm-commits@...r.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.19-rc1

Hi Andrew,

On Thu, 4 Dec 2025 at 14:29, Andrew Morton <akpm@...ux-foundation.org> wrote:
>       mm/page_alloc: prevent reporting pcp->batch = 0

I think, maybe, the following part of this patch broke nommu.

-       new_batch = max(1, zone_batchsize(zone));
+       new_batch = zone_batchsize(zone);

Before this change on nommu zone_batchsize() returns 0 but the max()
changes it to 1. Now it'll stay as 0 and anywhere that depends on it
not being 0 won't work?

I'm seeing a deadlock on nommu:

https://lore.kernel.org/lkml/20251211102607.2538595-1-daniel@thingy.jp/

Thanks,

Daniel