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

Message-Id: <20260116142635.b90464ed9772c146a9842370@linux-foundation.org>
Date: Fri, 16 Jan 2026 14:26:35 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Pratyush Yadav <pratyush@...nel.org>
Cc: Alexander Graf <graf@...zon.com>, Mike Rapoport <rppt@...nel.org>, 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, 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?