From: "Carlos López" <clopez@suse.de>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: kvm@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-riscv@lists.infradead.org, seanjc@google.com,
pbonzini@redhat.com, akpm@linux-foundation.org, david@kernel.org,
peterx@redhat.com, imbrenda@linux.ibm.com,
borntraeger@linux.ibm.com, frankja@linux.ibm.com,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
Peter Feiner <pfeiner@google.com>
Subject: Re: [PATCH v3 1/9] mm: fix eager write-bit restore for write-notified shared mappings
Date: Sun, 15 Nov 2026 23:00:53 +0100 [thread overview]
Message-ID: <f0a6bfcf-b131-419a-8b7d-ce10e0c507d8@suse.de> (raw)
In-Reply-To: <avd12eMWaTl87uL0@gremlin>
On 11/13/26 9:47 PM, Lorenzo Stoakes (ARM) wrote:
>> static inline bool vma_wants_manual_pte_write_upgrade(struct vm_area_struct *vma)
>> {
>> /*
>> @@ -596,19 +604,16 @@ static inline bool vma_wants_manual_pte_write_upgrade(struct vm_area_struct *vma
>> * if we can't do that automatically for all PTEs in a mapping. For
>> * private mappings, that's always the case when we have write
>> * permissions as we properly have to handle COW.
>> + *
>> + * vma->vm_page_prot lacks the write bit if writenotify is already
>> + * enabled, so pass it with the bits restored, as vma_set_page_prot()
>> + * does.
>
> We don't write code in comments.
I'll drop it.
>> */
>> if (vma->vm_flags & VM_SHARED)
>> - return vma_wants_writenotify(vma, vma->vm_page_prot);
>> + return vma_wants_writenotify(vma,
>> + vma_pgprot_modify(vma->vm_page_prot, vma->flags));
>
> You mention vma_set_page_prot() but then implement it differently from there and
> make no effort to abstract it?
>
> And so both callers now do the same thing, and both open code it... you should
> abstract that.
Okay, I'll add a helper for both.
next prev parent reply other threads:[~2026-11-15 22:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 14:20 [PATCH v3 0/9] KVM: don't zap secondary MMU on permission upgrade Carlos López
2026-11-12 14:20 ` [PATCH v3 1/9] mm: fix eager write-bit restore for write-notified shared mappings Carlos López
2026-11-13 20:47 ` Lorenzo Stoakes (ARM)
2026-11-15 22:00 ` Carlos López [this message]
2026-11-12 14:20 ` [PATCH v3 2/9] riscv: mm: add pud_soft_dirty() Carlos López
2026-11-12 14:20 ` [PATCH v3 3/9] mm/huge_memory: honor MM_CP_TRY_CHANGE_WRITABLE in change_huge_pud() Carlos López
2026-11-13 18:58 ` David Hildenbrand (Arm)
2026-11-15 22:00 ` Carlos López
2026-11-13 20:48 ` Lorenzo Stoakes (ARM)
2026-11-15 22:00 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 4/9] mm: keep writable entries writable on protection changes Carlos López
2026-11-13 18:56 ` David Hildenbrand (Arm)
2026-11-15 21:59 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 5/9] mm/mprotect: add MM_CP_PERM_UPGRADE Carlos López
2026-11-13 18:51 ` David Hildenbrand (Arm)
2026-11-15 22:03 ` Carlos López
2026-11-13 20:37 ` Lorenzo Stoakes (ARM)
2026-11-15 22:01 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 6/9] mm/mmu_notifier: add MMU_NOTIFIER_RANGE_PERM_UPGRADE Carlos López
2026-11-12 14:20 ` [PATCH v3 7/9] KVM: pass the mmu_notifier event and flags to kvm_gfn_range Carlos López
2026-11-12 14:20 ` [PATCH v3 8/9] KVM: x86/mmu: don't zap secondary MMU on permission upgrade Carlos López
2026-11-12 14:20 ` [PATCH v3 9/9] KVM: s390: don't unmap the gmap " Carlos López
2026-11-13 19:00 ` [PATCH v3 0/9] KVM: don't zap secondary MMU " David Hildenbrand (Arm)
2026-11-13 20:32 ` Lorenzo Stoakes (ARM)
2026-11-15 22:04 ` Carlos López
2026-11-13 20:59 ` Lorenzo Stoakes (ARM)
2026-11-15 22:19 ` Carlos López
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=f0a6bfcf-b131-419a-8b7d-ce10e0c507d8@suse.de \
--to=clopez@suse.de \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=jannh@google.com \
--cc=kvm@vger.kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=pfalcato@suse.de \
--cc=pfeiner@google.com \
--cc=seanjc@google.com \
--cc=vbabka@kernel.org \
/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
all inboxes | Powered by JetHome®