linux-kernel - Re: [PATCH v2 1/2] kho: use unsigned long for nr

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: <aW991CRBJ3QlNG2i@kernel.org>
Date: Tue, 20 Jan 2026 15:06:28 +0200
From: Mike Rapoport <rppt@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Pratyush Yadav <pratyush@...nel.org>, Alexander Graf <graf@...zon.com>,
	Pasha Tatashin <pasha.tatashin@...een.com>,
	kexec@...ts.infradead.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Suren Baghdasaryan <surenb@...gle.com>
Subject: Re: [PATCH v2 1/2] kho: use unsigned long for nr_pages

On Fri, Jan 16, 2026 at 02:26:35PM -0800, Andrew Morton wrote:
> On Fri, 16 Jan 2026 11:22:14 +0000 Pratyush Yadav <pratyush@...nel.org> wrote:
> 
> > With 4k pages, a 32-bit nr_pages can span up to 16 TiB. While it is a
> > lot, there exist systems with terabytes of RAM. gup is also moving to
> > using long for nr_pages. Use unsigned long and make KHO future-proof.
> 
> We can expect people to be using LTS kernel five years from now,
> perhaps much longer.  Machines will be bigger then!
> 
> IOW, shouldn't we backport this?

The latest LTS is 6.12 that still does not have KHO, I don't think it makes
sense to backport this to 6.18.

-- 
Sincerely yours,
Mike.