Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
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
Message-Id: <20221214200453.1772655-1-peterx@redhat.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

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