From: Hugh Dickins <hughd@google.com>
To: Peter Xu <peterx@redhat.com>
Cc: Hugh Dickins <hughd@google.com>,
Yuanzheng Song <songyuanzheng@huawei.com>,
akpm@linux-foundation.org, gregkh@linuxfoundation.org,
david@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH STABLE 5.10] mm/memory: add non-anonymous page check in the copy_present_page()
Date: Thu, 27 Oct 2022 14:58:02 -0700 (PDT) [thread overview]
Message-ID: <8aad435-bdc6-816f-2fe4-efe53abd6e5@google.com> (raw)
In-Reply-To: <Y1qdY8oUlUvWl067@x1n>
Let me delete stable from the Cc, this discussion is not for stable.
On Thu, 27 Oct 2022, Peter Xu wrote:
> On Wed, Oct 26, 2022 at 06:48:29PM -0700, Hugh Dickins wrote:
> >
> > And I imagined that the correct fix (short of going forward with David's
> > full changes) would be to back out to a context where one could add an
> > anon_vma_prepare(), then retry after that - involves dropping pt lock,
> > maybe gets nasty (tedious, anyway).
>
> Right, that looks a larger changeset with minimum benefit - the page is
> still inconsistent before fork(), and also for users don't fork() at all
> after the RO pin.
Sorry, I don't understand any of what you're saying there: but you appear
to be saying ("larger changeset with minimum benefit") that my suggestion
would not be worth the effort - fair enough, but...
>
> It looks to me Hugh's suggestion would be the best suite here for stable.
> Yuanzheng, what do you think?
... now you appear to be saying it would be worth the effort. Oh,
perhaps you're referring to just the change to check dst anon_vma:
perhaps, but I'm really having to guess at what you mean.
But none of that matters as much as below...
>
> For the long term I think we should wait for David's further unshare work
> so gup_must_unshare() will work for page caches too while mapped private.
I do wonder if in the long term we shall have to port all David's work
back to 5.15 and 5.10 (but I think there's yet more to come from him).
But set aside that thought for now...
More urgently, in the short term:
Peter, you've made no reference to David's mail, where he concludes that
Yuanzheng's !PageAnon patch is the appropriate one; and
David, you've made no reference to Peter's mail, where he concludes that
my doubts were correct, and it needs a different patch.
You appear to disagree over whether a RO-pinned file page needs to
be copied at fork() time. I don't know, but I hope you can agree
on that (in the 5.10 and 5.15 context: maybe David is thinking of
the 6.0 context and Peter of the 5.10 context) before going further.
(I'm hoping David is right, and I was plain wrong, since that's easiest.)
Hugh
next prev parent reply other threads:[~2022-10-27 21:58 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 [this message]
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
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=8aad435-bdc6-816f-2fe4-efe53abd6e5@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=songyuanzheng@huawei.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