linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.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>,
	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 15:17:39 -0700	[thread overview]
Message-ID: <20230414221739.GA54118@monkey> (raw)
In-Reply-To: <20230413231120.544685-2-peterx@redhat.com>

On 04/13/23 19:11, Peter Xu wrote:
> There're a bunch of things that were wrong:
> 
>   - Reading uffd-wp bit from a swap entry should use pte_swp_uffd_wp()
>     rather than huge_pte_uffd_wp().

That was/is quite confusing to me at least.

> 
>   - When copying over a pte, we should drop uffd-wp bit when
>     !EVENT_FORK (aka, when !userfaultfd_wp(dst_vma)).
> 
>   - When doing early CoW for private hugetlb (e.g. when the parent page was
>     pinned), uffd-wp bit should be properly carried over if necessary.
> 
> No bug reported probably because most people do not even care about these
> corner cases, but they are still bugs and can be exposed by the recent unit
> tests introduced, so fix all of them in one shot.
> 
> Cc: linux-stable <stable@vger.kernel.org>
> Fixes: bc70fbf269fd ("mm/hugetlb: handle uffd-wp during fork()")
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  mm/hugetlb.c | 26 ++++++++++++++++----------
>  1 file changed, 16 insertions(+), 10 deletions(-)

No issues except losing information in pte entry as pointed out by Mika.

-- 
Mike Kravetz


  parent reply	other threads:[~2023-04-14 22:17 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ä
2023-04-14 15:21         ` Peter Xu
2023-04-14 22:17   ` Mike Kravetz [this message]
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=20230414221739.GA54118@monkey \
    --to=mike.kravetz@oracle.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=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