From: Peter Xu <peterx@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: David Hildenbrand <david@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [PATCH v3 1/3] mm/mprotect: Fix soft-dirty check in can_change_pte_writable()
Date: Mon, 25 Jul 2022 09:59:18 -0400 [thread overview]
Message-ID: <Yt6htg03lqj7FFU2@xz-m1.local> (raw)
In-Reply-To: <C2910936-FDCF-4ECF-B014-D985284B225A@gmail.com>
On Fri, Jul 22, 2022 at 10:21:00AM -0700, Nadav Amit wrote:
> On Jul 22, 2022, at 12:08 AM, David Hildenbrand <david@redhat.com> wrote:
>
> >> +static inline bool vma_soft_dirty_enabled(struct vm_area_struct *vma)
> >> +{
> >> + /*
> >> + * NOTE: we must check this before VM_SOFTDIRTY on soft-dirty
> >> + * enablements, because when without soft-dirty being compiled in,
> >> + * VM_SOFTDIRTY is defined as 0x0, then !(vm_flags & VM_SOFTDIRTY)
> >> + * will be constantly true.
> >> + */
> >> + if (!IS_ENABLED(CONFIG_MEM_SOFT_DIRTY))
> >> + return false;
> >> +
> >> + /*
> >> + * Soft-dirty is kind of special: its tracking is enabled when the
> >> + * vma flags not set.
> >> + */
> >> + return !(vma->vm_flags & VM_SOFTDIRTY);
> >> +}
> >
> > That will come in handy in other patches I'm cooking.
>
> clear_refs_write() also comes to mind as well (for consistency; I see no
> correctness or performance issue).
I explicitly didn't touch that because current code is better..
mas_for_each(&mas, vma, ULONG_MAX) {
if (!(vma->vm_flags & VM_SOFTDIRTY))
continue;
vma->vm_flags &= ~VM_SOFTDIRTY;
vma_set_page_prot(vma);
}
It means when !CONFIG_MEM_SOFT_DIRTY the "if" will always be true and all
vma will be jumped.
If replaced with vma_soft_dirty_enabled() it'll be instead constantly false
returned. We'll redo vma_set_page_prot() even if unnecessary.
Here if we want to add the "CONFIG_MEM_SOFT_DIRTY" into equation it can be:
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index f8cd58846a28..ab6f2913b5a5 100644
--- a/fs/proc/task_mmu.c
+++ b/fs/proc/task_mmu.c
@@ -1290,6 +1290,8 @@ static ssize_t clear_refs_write(struct file *file, const char __user *buf,
}
if (type == CLEAR_REFS_SOFT_DIRTY) {
+ if (!IS_ENABLED(CONFIG_MEM_SOFT_DIRTY))
+ goto out_unlock;
mas_for_each(&mas, vma, ULONG_MAX) {
if (!(vma->vm_flags & VM_SOFTDIRTY))
continue;
Or even at the entrance to not take the mm sem. But it's not anything
important IMHO, so if no one asking for that I'll just leave it be.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2022-07-25 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 18:33 [PATCH v3 0/3] mm/mprotect: Fix soft-dirty checks Peter Xu
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 [this message]
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=Yt6htg03lqj7FFU2@xz-m1.local \
--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