userfaultfd-allow-registration-of-ranges-below-mmap_min_addr.patch removed from -mm tree
The quilt patch titled
Subject: userfaultfd: allow registration of ranges below mmap_min_addr
has been removed from the -mm tree. Its filename was
userfaultfd-allow-registration-of-ranges-below-mmap_min_addr.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: "Denis M. Karpov" <[email protected]>
Subject: userfaultfd: allow registration of ranges below mmap_min_addr
Date: Thu, 9 Apr 2026 13:33:45 +0300
The current implementation of validate_range() in fs/userfaultfd.c performs a hard check against mmap_min_addr. This is redundant because UFFDIO_REGISTER operates on memory ranges that must already be backed by a VMA.
Enforcing mmap_min_addr or capability checks again in userfaultfd is unnecessary and prevents applications like binary compilers from using UFFD for valid memory regions mapped by application.
Remove the redundant check for mmap_min_addr.
We started using UFFD instead of the classic mprotect approach in the binary translator to track application writes. During development, we encountered this bug. The translator cannot control where the translated application chooses to map its memory and if the app requires a low-address area, UFFD fails, whereas mprotect would work just fine. I believe this is a genuine logic bug rather than an improvement, and I would appreciate including the fix in stable.
---
fs/userfaultfd.c | 2 -- 1 file changed, 2 deletions(-)
fs/userfaultfd.c renamed from fs/userfaultfd.c~userfaultfd-allow-registration-of-ranges-below-mmap_min_addr +0 -2
@@ -1238,8 +1238,6 @@ static __always_inline int validate_unalreturn -EINVAL ;if (!len)return -EINVAL ; -if (start < mmap_min_addr) -return -EINVAL ;if (start >= task_size)return -EINVAL ;if (len > task_size - start)
_
Patches currently in -mm which might be from [email protected] are