From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Nadav Amit <nadav.amit@gmail.com>,
peterx@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: [PATCH v3 0/3] mm/mprotect: Fix soft-dirty checks
Date: Thu, 21 Jul 2022 14:33:35 -0400 [thread overview]
Message-ID: <20220721183338.27871-1-peterx@redhat.com> (raw)
v2: https://lore.kernel.org/lkml/20220720220324.88538-1-peterx@redhat.com/
Patch 1 is the previous patch and real fix. Two more test patches added to
add mprotect test to soft-dirty.c, meanwhile add soft-dirty test into the
vm test loop.
Please review, thanks.
Peter Xu (3):
mm/mprotect: Fix soft-dirty check in can_change_pte_writable()
selftests: soft-dirty: Add test for mprotect
selftests: Add soft-dirty into run_vmtests.sh
mm/internal.h | 18 ++++++
mm/mmap.c | 2 +-
mm/mprotect.c | 2 +-
tools/testing/selftests/vm/run_vmtests.sh | 2 +
tools/testing/selftests/vm/soft-dirty.c | 69 ++++++++++++++++++++++-
5 files changed, 90 insertions(+), 3 deletions(-)
--
2.32.0
next reply other threads:[~2022-07-21 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 18:33 Peter Xu [this message]
2022-07-21 18:33 ` [PATCH v3 1/3] mm/mprotect: Fix soft-dirty check in can_change_pte_writable() Peter Xu
2022-07-22 7:08 ` David Hildenbrand
2022-07-22 13:51 ` Peter Xu
2022-07-22 13:59 ` David Hildenbrand
2022-07-22 17:21 ` Nadav Amit
2022-07-25 13:59 ` Peter Xu
2022-07-25 14:11 ` David Hildenbrand
2022-07-21 18:33 ` [PATCH v3 2/3] selftests: soft-dirty: Add test for mprotect Peter Xu
2022-07-22 7:17 ` David Hildenbrand
2022-07-22 13:44 ` Peter Xu
2022-07-22 14:00 ` David Hildenbrand
2022-07-22 14:07 ` David Hildenbrand
2022-07-22 14:37 ` Peter Xu
2022-07-21 18:33 ` [PATCH v3 3/3] selftests: Add soft-dirty into run_vmtests.sh Peter Xu
2022-07-22 7:18 ` David Hildenbrand
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=20220721183338.27871-1-peterx@redhat.com \
--to=peterx@redhat.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 \
/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;
as well as URLs for NNTP newsgroup(s).