From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
xingwei lee <xrivendell7@gmail.com>,
yuxin wang <wang1315768607@163.com>,
Marius Fleischer <fleischermarius@gmail.com>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Rik van Riel <riel@surriel.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v3] x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()
Date: Thu, 3 Apr 2025 15:50:13 +0100 [thread overview]
Message-ID: <f190ca6e-c35a-4acd-b959-134452ec3c2f@lucifer.local> (raw)
In-Reply-To: <02a4ae57-ae97-42b7-86ba-78963bafed43@redhat.com>
On Thu, Apr 03, 2025 at 04:47:47PM +0200, David Hildenbrand wrote:
> On 02.04.25 14:32, Lorenzo Stoakes wrote:
> > For the whole thing with this fix-patch:
> >
> > Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> >
>
> So, we already have now
>
> commit dc84bc2aba85a1508f04a936f9f9a15f64ebfb31
> Author: David Hildenbrand <david@redhat.com>
> Date: Fri Mar 21 12:23:23 2025 +0100
>
> x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()
> So I'll only send a fixup (but will likely keep rc vs. ret unchanged for that).
I'm completely fine with either, as long as the fixup sorts the stupid
build isuses, the rest is fine, only nits :) Feel free to take tag for
things as-is (with fixup!).
>
> --
> Cheers,
>
> David / dhildenb
>
next prev parent reply other threads:[~2025-04-03 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 19:19 David Hildenbrand
2025-04-02 11:36 ` David Hildenbrand
2025-04-02 12:32 ` Lorenzo Stoakes
2025-04-03 14:47 ` David Hildenbrand
2025-04-03 14:50 ` Lorenzo Stoakes [this message]
2025-04-02 11:59 ` Lorenzo Stoakes
2025-04-02 12:20 ` David Hildenbrand
2025-04-02 12:31 ` Lorenzo Stoakes
2025-04-02 15:19 ` David Hildenbrand
2025-04-02 11:37 Lorenzo Stoakes
2025-04-03 15:14 ` [PATCH v3] x86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range() Dan Carpenter
2025-04-03 20:59 ` David Hildenbrand
2025-04-04 11:52 ` Lorenzo Stoakes
2025-04-04 12:20 ` David Hildenbrand
2025-04-04 12:27 ` David Hildenbrand
2025-04-06 17:17 ` Ingo Molnar
2025-04-07 7:11 ` Dan Carpenter
[not found] <202503270941.IFILyNCX-lkp@intel.com>
[not found] ` <9b3b3296-ab21-418b-a0ff-8f5248f9b4ec@lucifer.local>
[not found] ` <b21bcd61-faf0-4ad8-b644-99794794594f@redhat.com>
2025-04-02 11:40 ` Lorenzo Stoakes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f190ca6e-c35a-4acd-b959-134452ec3c2f@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dan.carpenter@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=fleischermarius@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=torvalds@linux-foundation.org \
--cc=wang1315768607@163.com \
--cc=x86@kernel.org \
--cc=xrivendell7@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox