From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,thehajime@gmail.com,stable@vger.kernel.org,ljs@kernel.org,liam@infradead.org,tasos.papagiannnis@gmail.com,akpm@linux-foundation.org
Subject: [merged mm-stable] mm-nommu-reject-wrapping-ranges-in-access_remote_vm.patch removed from -mm tree
Date: Thu, 08 Oct 2026 22:57:53 -0700 [thread overview]
Message-ID: <20261009055754.5D92F1F000FF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/nommu: reject wrapping ranges in access_remote_vm()
has been removed from the -mm tree. Its filename was
mm-nommu-reject-wrapping-ranges-in-access_remote_vm.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: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Subject: mm/nommu: reject wrapping ranges in access_remote_vm()
Date: Wed, 9 Sep 2026 09:42:31 +0300
The NOMMU implementation of access_process_vm() rejects address ranges
whose end wraps around, but access_remote_vm() bypasses this check even
though both functions delegate to __access_remote_vm().
Move the wraparound check into __access_remote_vm() so it applies to both
entry points.
This is originally reported in [1].
Link: https://lore.kernel.org/20260909064231.18693-1-tasos.papagiannnis@gmail.com
Fixes: f55f199b7d76 ("NOMMU: implement access_remote_vm")
Signed-off-by: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Closes: https://lore.kernel.org/bpf/4ef240a5bea36ff84df9589671367832860795159386a4c8fba546a0fa8b786f@mail.kernel.org/ [1]
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Hajime Tazaki <thehajime@gmail.com>
Cc: <stable@vger.kernel.org>
---
mm/nommu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/mm/nommu.c~mm-nommu-reject-wrapping-ranges-in-access_remote_vm
+++ a/mm/nommu.c
@@ -1674,6 +1674,9 @@ static int __access_remote_vm(struct mm_
struct vm_area_struct *vma;
int write = gup_flags & FOLL_WRITE;
+ if (addr + len < addr)
+ return 0;
+
if (mmap_read_lock_killable(mm))
return 0;
@@ -1727,9 +1730,6 @@ int access_process_vm(struct task_struct
{
struct mm_struct *mm;
- if (addr + len < addr)
- return 0;
-
mm = get_task_mm(tsk);
if (!mm)
return 0;
_
Patches currently in -mm which might be from tasos.papagiannnis@gmail.com are
reply other threads:[~2026-10-09 5:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261009055754.5D92F1F000FF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=liam@infradead.org \
--cc=ljs@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tasos.papagiannnis@gmail.com \
--cc=thehajime@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.