From: Miaohe Lin <linmiaohe@huawei.com>
To: Peter Xu <peterx@redhat.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Pengfei Xu <pengfei.xu@intel.com>,
Nadav Amit <nadav.amit@gmail.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] mm/uffd: Fix pte marker when fork() without fork event
Date: Sat, 17 Dec 2022 10:59:06 +0800 [thread overview]
Message-ID: <eeedfdcb-2f9a-86fb-ab62-32cdfaf5d289@huawei.com> (raw)
In-Reply-To: <20221214200453.1772655-2-peterx@redhat.com>
On 2022/12/15 4:04, Peter Xu wrote:
> When fork(), dst_vma is not guaranteed to have VM_UFFD_WP even if src may
> have it and has pte marker installed. The warning is improper along with
> the comment. The right thing is to inherit the pte marker when needed, or
> keep the dst pte empty.
>
> A vague guess is this happened by an accident when there's the prior patch
> to introduce src/dst vma into this helper during the uffd-wp feature got
> developed and I probably messed up in the rebase, since if we replace
> dst_vma with src_vma the warning & comment it all makes sense too.
>
> Hugetlb did exactly the right here (copy_hugetlb_page_range()). Fix the
> general path.
>
> Reproducer:
>
> https://github.com/xupengfe/syzkaller_logs/blob/main/221208_115556_copy_page_range/repro.c
>
> Cc: <stable@vger.kernel.org> # 5.19+
> Fixes: c56d1b62cce8 ("mm/shmem: handle uffd-wp during fork()")
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=216808
> Reported-by: Pengfei Xu <pengfei.xu@intel.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Looks good to me. Thanks.
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks,
Miaohe Lin
next prev parent reply other threads:[~2022-12-17 2:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 20:04 [PATCH 0/2] mm: Fixes on pte markers Peter Xu
2022-12-14 20:04 ` [PATCH 1/2] mm/uffd: Fix pte marker when fork() without fork event Peter Xu
2022-12-16 9:04 ` David Hildenbrand
2022-12-16 14:54 ` Peter Xu
2022-12-16 15:57 ` David Hildenbrand
2022-12-16 16:24 ` Peter Xu
2022-12-16 16:37 ` David Hildenbrand
2022-12-17 2:59 ` Miaohe Lin [this message]
2022-12-14 20:04 ` [PATCH 2/2] mm: Fix a few rare cases of using swapin error pte marker Peter Xu
2022-12-15 7:12 ` Huang, Ying
2022-12-15 14:05 ` Peter Xu
2022-12-16 0:06 ` Huang, Ying
2022-12-16 16:01 ` David Hildenbrand
2022-12-16 16:04 ` David Hildenbrand
2022-12-17 2:59 ` Miaohe Lin
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=eeedfdcb-2f9a-86fb-ab62-32cdfaf5d289@huawei.com \
--to=linmiaohe@huawei.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=pengfei.xu@intel.com \
--cc=peterx@redhat.com \
--cc=stable@vger.kernel.org \
--cc=ying.huang@intel.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