[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250319102441.GBZ9qbaZfRWdYFIknU@fat_crate.local>
Date: Wed, 19 Mar 2025 11:24:41 +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 11:16:36AM +0100, David Hildenbrand wrote:
> Ahh, the commit id is already supposed to be stable, got it.
Yap, we try to avoid rebasing when it becomes really hairy and the commits
have been stable and out there for a while...
> I'm currently testing the following as fix, that avoids the second lookup
> completely.
Cool, please holler asap what happens so that we can act accordingly.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists