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: <CAHk-=wj681NMt4ofHWVDzbcb2CjyAZWnVYX=9eJ5tmYjEONNBA@mail.gmail.com>
Date: Fri, 5 Dec 2025 19:43:52 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Ankit Agrawal <ankita@...dia.com>, 
	Alex Williamson <alex@...zbot.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

On Fri, 5 Dec 2025 at 18:54, Jason Gunthorpe <jgg@...dia.com> wrote:
>
> Reverting it now works well enough too. Let's see if Ankit can prepare
> a new revision and perhaps Alex can forward it next week or very early
> rc1 after LPC.

So adding that memory poisoning logic at mmap time looks crazy to me.
The mmap has *nothing* to do with memory poisoning. The memory is
there whether it is mapped or not, and admittedly it's harder to
_access_ when not mapped, but it still has nothing to do with mmap.

As far as I can tell, that memory poisoning logic should be
added/removed when the device is registered or unregistered, and there
is nothing about mmap that should have any effect what-so-ever.

                     Linus