From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Nadav Amit <nadav.amit@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
peterx@redhat.com, Andrea Arcangeli <aarcange@redhat.com>,
Ives van Hoorne <ives@codesandbox.io>,
Axel Rasmussen <axelrasmussen@google.com>,
Alistair Popple <apopple@nvidia.com>
Subject: [PATCH v3 0/2] mm/migrate: Fix writable pte for read migration entry
Date: Sun, 13 Nov 2022 19:04:45 -0500 [thread overview]
Message-ID: <20221114000447.1681003-1-peterx@redhat.com> (raw)
v3:
- Go back to use WARN_ON_ONCE because mmdebug.h not included in
arch/x86/include/asm/pgtable.h
- Added r-b and t-b
- s/symbton/symbtom/ [Nadav]
- Updated commit message of patch 1, removing mprotect example
v2:
- Replace WARN_ON_ONCE with VM_WARN_ON_ONCE in patch 2 [Nadav]
This comes from a report from Ives on using uffd-wp on shmem. More
information can be found in patch 1 commit message.
Patch 2 added some more sanity check when walking pgtables and when we
convert the ptes into other forms e.g. for migration and swap. It will
make the error trigger even earlier than the user could notice, meanwhile
nail down the case if it's a wrong pgtable setup.
We probably need patch 1 for stable (5.19+). Please have a look, thanks.
Peter Xu (2):
mm/migrate: Fix read-only page got writable when recover pte
mm/uffd: Sanity check write bit for uffd-wp protected ptes
arch/x86/include/asm/pgtable.h | 18 +++++++++++++++++-
mm/migrate.c | 8 +++++++-
2 files changed, 24 insertions(+), 2 deletions(-)
--
2.37.3
next reply other threads:[~2022-11-14 0:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 0:04 Peter Xu [this message]
2022-11-14 0:04 ` [PATCH v3 1/2] mm/migrate: Fix read-only page got writable when recover pte Peter Xu
2022-11-15 18:17 ` David Hildenbrand
2022-11-30 22:24 ` Andrew Morton
2022-12-01 15:28 ` Peter Xu
2022-12-01 15:42 ` David Hildenbrand
2022-12-01 22:30 ` Andrew Morton
2022-12-02 11:03 ` David Hildenbrand
2022-12-02 12:07 ` David Hildenbrand
2022-12-02 15:14 ` Peter Xu
2022-12-02 15:40 ` David Hildenbrand
2022-12-02 17:18 ` David Hildenbrand
2022-11-14 0:04 ` [PATCH v3 2/2] mm/uffd: Sanity check write bit for uffd-wp protected ptes 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=20221114000447.1681003-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=axelrasmussen@google.com \
--cc=ives@codesandbox.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=rppt@linux.vnet.ibm.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