From: "Mika Penttilä" <mpenttil@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Axel Rasmussen <axelrasmussen@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Nadav Amit <nadav.amit@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/6] mm/hugetlb: Fix uffd-wp during fork()
Date: Fri, 14 Apr 2023 17:23:12 +0300 [thread overview]
Message-ID: <d14ddbc6-5315-78a2-cdfa-72a77d3603dd@redhat.com> (raw)
In-Reply-To: <ZDlet0+oZ2nrnUdu@x1n>
On 14.4.2023 17.09, Peter Xu wrote:
> On Fri, Apr 14, 2023 at 12:45:29PM +0300, Mika Penttilä wrote:
>>> } else if (unlikely(is_hugetlb_entry_migration(entry))) {
>>> swp_entry_t swp_entry = pte_to_swp_entry(entry);
>>> - bool uffd_wp = huge_pte_uffd_wp(entry);
>
> [1]
>
>>> if (!is_readable_migration_entry(swp_entry) && cow) {
>>> /*
>>> @@ -5049,11 +5050,12 @@ int copy_hugetlb_page_range(struct mm_struct *dst, struct mm_struct *src,
>>> swp_entry = make_readable_migration_entry(
>>> swp_offset(swp_entry));
>>> entry = swp_entry_to_pte(swp_entry);
>
> [2]
>
>>> - if (userfaultfd_wp(src_vma) && uffd_wp)
>>> - entry = huge_pte_mkuffd_wp(entry);
>>> + if (userfaultfd_wp(src_vma) &&
>>> + pte_swp_uffd_wp(entry))
>>> + entry = pte_swp_mkuffd_wp(entry);
>>
>>
>> This looks interesting with pte_swp_uffd_wp and pte_swp_mkuffd_wp ?
>
> Could you explain what do you mean?
>
Yes like you noticed also you called pte_swp_mkuffd_wp(entry) iff
pte_swp_uffd_wp(entry) which is of course a nop.
But the fixup not dropping the temp var should work.
> I think these helpers are the right ones to use, as afaict hugetlb
> migration should follow the same pte format with !hugetlb. However, I
> noticed I did it wrong when dropping the temp var - when at [1], "entry"
> still points to the src entry, but at [2] it's already pointing to the
> newly created one.. so I think I can't drop the var, a fixup should like:
>
> ===8<===
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 083aae35bff8..cd3a9d8f4b70 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -5041,6 +5041,7 @@ int copy_hugetlb_page_range(struct mm_struct *dst, struct mm_struct *src,
> set_huge_pte_at(dst, addr, dst_pte, entry);
> } else if (unlikely(is_hugetlb_entry_migration(entry))) {
> swp_entry_t swp_entry = pte_to_swp_entry(entry);
> + bool uffd_wp = pte_swp_uffd_wp(entry);
>
> if (!is_readable_migration_entry(swp_entry) && cow) {
> /*
> @@ -5050,8 +5051,7 @@ int copy_hugetlb_page_range(struct mm_struct *dst, struct mm_struct *src,
> swp_entry = make_readable_migration_entry(
> swp_offset(swp_entry));
> entry = swp_entry_to_pte(swp_entry);
> - if (userfaultfd_wp(src_vma) &&
> - pte_swp_uffd_wp(entry))
> + if (userfaultfd_wp(src_vma) && uffd_wp)
> entry = pte_swp_mkuffd_wp(entry);
> set_huge_pte_at(src, addr, src_pte, entry);
> ===8<===
>
> Besides, did I miss something else?
>
> Thanks,
>
--Mika
next prev parent reply other threads:[~2023-04-14 14:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 23:11 [PATCH 0/6] mm/hugetlb: More fixes around uffd-wp vs fork() / RO pins Peter Xu
2023-04-13 23:11 ` [PATCH 1/6] mm/hugetlb: Fix uffd-wp during fork() Peter Xu
2023-04-14 9:37 ` David Hildenbrand
2023-04-14 9:45 ` Mika Penttilä
2023-04-14 14:09 ` Peter Xu
2023-04-14 14:23 ` Mika Penttilä [this message]
2023-04-14 15:21 ` Peter Xu
2023-04-14 22:17 ` Mike Kravetz
2023-04-13 23:11 ` [PATCH 2/6] mm/hugetlb: Fix uffd-wp bit lost when unsharing happens Peter Xu
2023-04-14 9:23 ` David Hildenbrand
2023-04-14 22:19 ` Mike Kravetz
2023-04-13 23:11 ` [PATCH 3/6] selftests/mm: Add a few options for uffd-unit-test Peter Xu
2023-04-13 23:11 ` [PATCH 4/6] selftests/mm: Extend and rename uffd pagemap test Peter Xu
2023-04-13 23:11 ` [PATCH 5/6] selftests/mm: Rename COW_EXTRA_LIBS to IOURING_EXTRA_LIBS Peter Xu
2023-04-14 9:52 ` David Hildenbrand
2023-04-14 13:56 ` Peter Xu
2023-04-14 14:29 ` David Hildenbrand
2023-04-13 23:12 ` [PATCH 6/6] selftests/mm: Add tests for RO pinning vs fork() Peter Xu
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=d14ddbc6-5315-78a2-cdfa-72a77d3603dd@redhat.com \
--to=mpenttil@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=peterx@redhat.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