linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Pengfei Xu <pengfei.xu@intel.com>,
	peterx@redhat.com, Nadav Amit <nadav.amit@gmail.com>,
	David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Huang Ying <ying.huang@intel.com>
Subject: [PATCH 0/2] mm: Fixes on pte markers
Date: Wed, 14 Dec 2022 15:04:51 -0500	[thread overview]
Message-ID: <20221214200453.1772655-1-peterx@redhat.com> (raw)

Patch 1 resolves the syzkiller report from Pengfei.

Patch 2 further harden pte markers when used with the recent swapin error
markers.  The major case is we should persist a swapin error marker after
fork(), so child shouldn't read a corrupted page.

No report so far with patch 2, but it can be somehow tested with things
like:
https://github.com/xzpeter/clibs/blob/master/misc/pageout.c
Plus some hacks.

Please have a look, thanks.

Peter Xu (2):
  mm/uffd: Fix pte marker when fork() without fork event
  mm: Fix a few rare cases of using swapin error pte marker

 mm/hugetlb.c  |  3 +++
 mm/memory.c   | 14 +++++++-------
 mm/mprotect.c |  8 +++++++-
 3 files changed, 17 insertions(+), 8 deletions(-)

-- 
2.37.3



             reply	other threads:[~2022-12-14 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 20:04 Peter Xu [this message]
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

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=20221214200453.1772655-1-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nadav.amit@gmail.com \
    --cc=pengfei.xu@intel.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