mm-mremap-use-an-explicit-uffd-failure-path-for-mremap.patch removed from -mm tree
The quilt patch titled
Subject: mm/mremap: use an explicit uffd failure path for mremap
has been removed from the -mm tree. Its filename was
mm-mremap-use-an-explicit-uffd-failure-path-for-mremap.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Lorenzo Stoakes <[email protected]>
Subject: mm/mremap: use an explicit uffd failure path for mremap
Date: Thu, 17 Jul 2025 17:55:55 +0100
Right now it appears that the code is relying upon the returned destination address having bits outside PAGE_MASK to indicate whether an error value is specified, and decrementing the increased refcount on the uffd ctx if so.
This is not a safe means of determining an error value, so instead, be specific. It makes far more sense to do so in a dedicated error path, so add mremap_userfaultfd_fail() for this purpose and use this when an error arises.
A vm_userfaultfd_ctx is not established until we are at the point where mremap_userfaultfd_prep() is invoked in copy_vma_and_data(), so this is a no-op until this happens.
That is - uffd remap notification only occurs if the VMA is actually moved
- at which point a UFFD_EVENT_REMAP event is raised.
No errors can occur after this point currently, though it's certainly not guaranteed this will always remain the case, and we mustn't rely on this.
However, the reason for needing to handle this case is that, when an error arises on a VMA move at the point of adjusting page tables, we revert this operation, and propagate the error.
At this point, it is not correct to raise a uffd remap event, and we must handle it.
This refactoring makes it abundantly clear what we are doing.
We assume vrm->new_addr is always valid, which a prior change made the case even for mremap() invocations which don't move the VMA, however given no uffd context would be set up in this case it's immaterial to this change anyway.
No functional change intended.
---
fs/userfaultfd.c | 15 ++++++++++----- include/linux/userfaultfd_k.h | 5 +++++ mm/mremap.c | 16 ++++++++++++---- 3 files changed, 27 insertions(+), 9 deletions(-)
fs/userfaultfd.c renamed from fs/userfaultfd.c~mm-mremap-use-an-explicit-uffd-failure-path-for-mremap +10 -5
@@ -750,11 +750,6 @@ void mremap_userfaultfd_complete(structif (!ctx)return ; -if (to & ~PAGE_MASK ) { -userfaultfd_ctx_put (ctx); -return ; - } -msg_init (&ewq.msg); ewq.msg.event =UFFD_EVENT_REMAP ;
@@ -765,6 +760,16 @@ void mremap_userfaultfd_complete(structuserfaultfd_event_wait_completion (ctx, &ewq); } +void mremap_userfaultfd_fail (struct vm_userfaultfd_ctx *vm_ctx) +{ +struct userfaultfd_ctx *ctx = vm_ctx->ctx; + +if (!ctx) +return ; + +userfaultfd_ctx_put (ctx); +} +bool userfaultfd_remove (struct vm_area_struct *vma,unsigned long start,unsigned long end) {
include/linux/userfaultfd_k.h renamed from include/linux/userfaultfd_k.h~mm-mremap-use-an-explicit-uffd-failure-path-for-mremap +5 -0
@@ -259,6 +259,7 @@ extern void mremap_userfaultfd_prep(struextern void mremap_userfaultfd_complete (struct vm_userfaultfd_ctx *,unsigned long from,unsigned long to,unsigned long len); +void mremap_userfaultfd_fail (struct vm_userfaultfd_ctx *); extern bool userfaultfd_remove(struct vm_area_struct *vma, unsigned long start,
@@ -371,6 +372,10 @@ static inline void mremap_userfaultfd_co { } +static inline void mremap_userfaultfd_fail (struct vm_userfaultfd_ctx *ctx) +{ +} +static inline bool userfaultfd_remove (struct vm_area_struct *vma,unsigned long start,unsigned long end)
mm/mremap.c renamed from mm/mremap.c~mm-mremap-use-an-explicit-uffd-failure-path-for-mremap +12 -4
@@ -1729,12 +1729,17 @@ static int check_prep_vma(struct vma_remreturn 0 ; } -static void notify_uffd (struct vma_remap_struct *vrm,unsigned long to) +static void notify_uffd (struct vma_remap_struct *vrm,bool failed) {struct mm_struct *mm = current->mm; +/* Regardless of success/failure, we always notify of any unmaps. */ userfaultfd_unmap_complete (mm, vrm->uf_unmap_early); -mremap_userfaultfd_complete (vrm->uf, vrm->addr, to, vrm->old_len); +if (failed) +mremap_userfaultfd_fail (vrm->uf); +else +mremap_userfaultfd_complete (vrm->uf, vrm->addr, + vrm->new_addr, vrm->old_len);userfaultfd_unmap_complete (mm, vrm->uf_unmap); }
@@ -1742,6 +1747,7 @@ static unsigned long do_mremap(struct vm {struct mm_struct *mm = current->mm;unsigned long res; +bool failed; vrm->old_len =PAGE_ALIGN (vrm->old_len); vrm->new_len =PAGE_ALIGN (vrm->new_len);
@@ -1763,13 +1769,15 @@ static unsigned long do_mremap(struct vm res =vrm_implies_new_addr (vrm) ?mremap_to (vrm) :mremap_at (vrm); out: + failed =IS_ERR_VALUE (res); +if (vrm->mmap_locked)mmap_write_unlock (mm); -if (!IS_ERR_VALUE (res) && vrm->mlocked && vrm->new_len > vrm->old_len) +if (!failed && vrm->mlocked && vrm->new_len > vrm->old_len)mm_populate (vrm->new_addr + vrm->old_len, vrm->delta); -notify_uffd (vrm, res); +notify_uffd (vrm, failed);return res; }
_
Patches currently in -mm which might be from [email protected] are
mm-mseal-always-define-vm_sealed.patch mm-mseal-update-madvise-logic.patch mm-mseal-small-cleanups.patch mm-mseal-simplify-and-rename-vma-gap-check.patch mm-mseal-rework-mseal-apply-logic.patch maintainers-add-missing-percpu-internalh-file-to-per-cpu-section.patch maintainers-add-missing-interval_treec-to-memory-mapping-section.patch maintainers-add-missing-mm_sloth-file-thp-section.patch maintainers-add-missing-mm_sloth-file-thp-section-fix.patch maintainers-move-memremap-to-hotplug-section.patch maintainers-add-missing-shrinker-files.patch maintainers-add-missing-files-to-page-alloc-section.patch maintainers-add-missing-zsmalloc-file.patch maintainers-add-mm-misc-section-add-missing-files-to-misc-and-core.patch maintainers-add-missing-file-to-cgroup-section.patch