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>
Subject: Re: [PATCH 2/2] mm: Fix a few rare cases of using swapin error pte marker
Date: Sat, 17 Dec 2022 10:59:46 +0800 [thread overview]
Message-ID: <9669705e-1bee-c789-86c7-6e3f6e28d109@huawei.com> (raw)
In-Reply-To: <20221214200453.1772655-3-peterx@redhat.com>
On 2022/12/15 4:04, Peter Xu wrote:
> This patch should harden commit 15520a3f0469 ("mm: use pte markers for swap
> errors") on using pte markers for swapin errors on a few corner cases.
>
> 1. Propagate swapin errors across fork()s: if there're swapin errors in
> the parent mm, after fork()s the child should sigbus too when an error
> page is accessed.
>
> 2. Fix a rare condition race in pte_marker_clear() where a uffd-wp pte
> marker can be quickly switched to a swapin error.
>
> 3. Explicitly ignore swapin error pte markers in change_protection().
>
> I mostly don't worry on (2) or (3) at all, but we should still have them.
> Case (1) is special because it can potentially cause silent data corrupt on
> child when parent has swapin error triggered with swapoff, but since swapin
> error is rare itself already it's probably not easy to trigger either.
>
> Currently there is a priority difference between the uffd-wp bit and the
> swapin error entry, in which the swapin error always has higher
> priority (e.g. we don't need to wr-protect a swapin error pte marker).
>
> If there will be a 3rd bit introduced, we'll probably need to consider a
> more involved approach so we may need to start operate on the bits. Let's
> leave that for later.
>
> This patch is tested with case (1) explicitly where we'll get corrupted
> data before in the child if there's existing swapin error pte markers, and
> after patch applied the child can be rightfully killed.
>
> We don't need to copy stable for this one since 15520a3f0469 just landed as
> part of v6.2-rc1, only "Fixes" applied.
>
> Fixes: 15520a3f0469 ("mm: use pte markers for swap errors")
> Signed-off-by: Peter Xu <peterx@redhat.com>
Looks good to me. Thanks.
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks,
Miaohe Lin
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
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 [this message]
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=9669705e-1bee-c789-86c7-6e3f6e28d109@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=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