From: Peter Xu <peterx@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: Yuanzheng Song <songyuanzheng@huawei.com>,
akpm@linux-foundation.org, gregkh@linuxfoundation.org,
david@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH STABLE 5.10] mm/memory: add non-anonymous page check in the copy_present_page()
Date: Fri, 28 Oct 2022 10:39:59 -0400 [thread overview]
Message-ID: <Y1vpvzaU322ENcEc@x1n> (raw)
In-Reply-To: <432c4428-b6d4-f93-266-b920a854c3c@google.com>
On Thu, Oct 27, 2022 at 06:32:01PM -0700, Hugh Dickins wrote:
> Sorry for leading everyone astray: my mistake was to suppose that
> its !PageAnon check was simply to avoid the later BUG_ON(!anon_vma):
> whereas David and Peter now agree that it actually corrects the
> semantics for fork() on file pages.
Thanks for raising this from the start, Hugh. It's definitely worthwhile
to discuss this topic which is not obvious at all at least to me, and merge
even the same patch would be different before/after such a discussion,
since we're clearer on the side effects.
>
> I lift my hold on Yuanzheng's patch: nobody actually said "Acked-by",
> but I think the discussion and resolution have given better than that.
> (No 3rd thoughts please!)
I've acked directly on v2, note that after this discussion IMHO the comment
of !Anon check can be slightly improved (e.g. add some more information on
why we decided to not copy the page even if anon_vma existed), but I don't
want to be harsh on any stable backports that helps resolving problems
already in correct ways.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2022-10-28 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:49 Yuanzheng Song
2022-10-26 16:52 ` Greg KH
2022-10-27 11:37 ` songyuanzheng
2022-10-26 21:51 ` Hugh Dickins
2022-10-27 0:32 ` Peter Xu
2022-10-27 1:48 ` Hugh Dickins
2022-10-27 2:11 ` songyuanzheng
2022-10-27 15:01 ` Peter Xu
2022-10-27 21:58 ` Hugh Dickins
2022-10-27 22:56 ` Peter Xu
2022-10-28 1:32 ` Hugh Dickins
2022-10-28 4:26 ` David Hildenbrand
2022-10-28 14:39 ` Peter Xu [this message]
2022-10-27 7:54 ` David Hildenbrand
2022-10-27 11:55 ` songyuanzheng
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=Y1vpvzaU322ENcEc@x1n \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songyuanzheng@huawei.com \
--cc=stable@vger.kernel.org \
/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