From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
liam@infradead.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/nommu: Reject wrapping ranges in access_remote_vm()
Date: Fri, 25 Sep 2026 14:20:33 +0100 [thread overview]
Message-ID: <arZzn0bwWqp7xTE5@gremlin> (raw)
In-Reply-To: <20260909064231.18693-1-tasos.papagiannnis@gmail.com>
BTW always feel free to nag if you're not getting review! Something things
get missed. (Though I'd say wait at least a couple weeks before doing
that!)
On Wed, Sep 09, 2026 at 09:42:31AM +0300, Anastasios Papagiannis wrote:
> 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].
>
> [1] https://lore.kernel.org/bpf/4ef240a5bea36ff84df9589671367832860795159386a4c8fba546a0fa8b786f@mail.kernel.org/
Probably better to drop this big and make this a Link: tag.
>
> Fixes: f55f199b7d76 ("NOMMU: implement access_remote_vm")
Cc: stable I think?
> Signed-off-by: Anastasios Papagiannis <tasos.papagiannnis@gmail.com>
Seems reasonable to me! So:
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> mm/nommu.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 498e01ee40b0..ed44510e3770 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -1674,6 +1674,9 @@ static int __access_remote_vm(struct mm_struct *mm, unsigned long addr,
> 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 *tsk, unsigned long addr, void *buf, in
> {
> struct mm_struct *mm;
>
> - if (addr + len < addr)
> - return 0;
> -
> mm = get_task_mm(tsk);
> if (!mm)
> return 0;
>
> base-commit: 0d9ff90a5422cc7509258aaaba1e7481df4d332a
> --
> 2.55.0
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-09-25 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 6:42 [PATCH] mm/nommu: Reject wrapping ranges in access_remote_vm() Anastasios Papagiannis
2026-09-09 7:13 ` Andrew Morton
2026-09-09 20:11 ` Hajime Tazaki
2026-09-25 13:08 ` Lorenzo Stoakes (ARM)
2026-09-25 13:20 ` Lorenzo Stoakes (ARM) [this message]
2026-09-25 23:04 ` Andrew Morton
2026-09-28 15:04 ` Anastasios Papagiannis
2026-09-28 15:07 ` Lorenzo Stoakes (ARM)
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=arZzn0bwWqp7xTE5@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tasos.papagiannnis@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.