linux-kernel - Re: [PATCH] mm: fix apply_to_existing_page

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: <zfzh7665tzqmludh6ic5oaxidm44ewkel7t2nj5hvg6qppepnl@mj7dp7rkprcy>
Date: Wed, 9 Apr 2025 13:41:03 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: David Hildenbrand <david@...hat.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>, 
	Andrew Morton <akpm@...ux-foundation.org>, Vlastimil Babka <vbabka@...e.cz>, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, Daniel Axtens <dja@...ens.net>
Subject: Re: [PATCH] mm: fix apply_to_existing_page_range()

On Wed, Apr 09, 2025 at 12:26:09PM +0200, David Hildenbrand wrote:
> > > It should affect apply_to_existing_page_range() users where create==false.
> > > There are not many, and likely most PTEs in the range they are passing are
> > > all non-none.
> > 
> > Or we just silently leak memory :P
> 
> That's exactly what I am trying to figure out: is there something upstream
> that could actually run into this such that we should CC stable?

>From a quick glance, I don't see any of them to have a problem, but the
fix is trivial enough for stable@ even without a known buggy user.

-- 
  Kiryl Shutsemau / Kirill A. Shutemov