[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <faa04276-a4d7-48af-8957-9123cc09f66b@redhat.com>
Date: Wed, 19 Mar 2025 11:27:19 +0100
From: David Hildenbrand <david@...hat.com>
To: Borislav Petkov <bp@...en8.de>
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 19.03.25 11:24, Borislav Petkov wrote:
> 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.
Yes, expect it later today -- have to refresh my brain how I managed to
reproduce the original issue.
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists