linux-kernel - Re: [tip: x86/mm] x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250319095357.GAZ9qUNaWSORZMXdRK@fat_crate.local>
Date: Wed, 19 Mar 2025 10:53:57 +0100
From: Borislav Petkov <bp@...en8.de>
To: David Hildenbrand <david@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
	xingwei lee <xrivendell7@...il.com>,
	yuxin wang <wang1315768607@....com>,
	Marius Fleischer <fleischermarius@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Andy Lutomirski <luto@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Rik van Riel <riel@...riel.com>, "H. Peter Anvin" <hpa@...or.com>,
	Peter Xu <peterx@...hat.com>, x86@...nel.org,
	Dan Carpenter <dan.carpenter@...aro.org>
Subject: Re: [tip: x86/mm] x86/mm/pat: Fix VM_PAT handling when fork() fails
 in copy_page_range()

On Wed, Mar 19, 2025 at 09:15:25AM +0100, David Hildenbrand wrote:
> @Ingo, can you drop this patch for now? It's supposed to be "!get_pat_info"
> here, and I want to re-verify now that a couple of months passed, whether
> it's all working as expected with that.
> 
> (we could actually complain if get_pat_info() would fail at this point, let
> me think about that)
> 
> I'll resend once I get to it. Thanks!

That patch is deep into the x86/mm branch. We could

- rebase: not good, especially one week before the merge window

- send a revert: probably better along with an explanation why we're reverting

- do a small fix which disables it ontop

- fix it properly: probably best! :-)

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette