All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "James Houghton" <jthoughton@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH 07/10] uaccess: Fail user nofault helpers quietly when current->mm is NULL
Date: Mon, 26 Oct 2026 22:11:33 +0000	[thread overview]
Message-ID: <sashiko-outbox-185785@kernel.org> (raw)
In-Reply-To: <20261026215226.3713941-8-jthoughton@google.com>

> The user nofault helpers (copy_{from,to}_user_nofault(),
> strncpy_from_user_nofault() and strnlen_user_nofault()) are meant to be
> callable from any context, e.g. from BPF programs, kprobes or perf, which
> may run on behalf of a kernel thread or of a task that has already gone
> through exit_mm(). In such a context, there is no user memory to access,
> and the right answer is simply to fail.
> 
> Since the previous commit, the uaccess helpers they use warn when
> current->mm is NULL, e.g. bpf_probe_read_user_str() from a BPF program
> attached to a function called by a kernel thread would now trip the
> WARN_ON_ONCE() in strncpy_from_user().
> 
> Check for a NULL current->mm up front in these helpers, and fail without
> warning and without attempting the access.
> 
> On x86, copy_from_user_nofault() was already refusing such accesses, as
> nmi_uaccess_okay() returns false when current->mm is not the loaded mm.
> 
> For the same reason, make copy_to_user_iter_nofault() use
> should_fail_usercopy() directly, leaving the NULL mm check to
> copy_to_user_nofault().
> 
> Signed-off-by: James Houghton <jthoughton@google.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261026215226.3713941-1-jthoughton@google.com?part=7


  reply	other threads:[~2026-10-26 22:11 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 21:52 [RFC PATCH 00/10] uaccess: Refuse and warn on user accesses when current->mm is NULL James Houghton
2026-10-26 21:52 ` [RFC PATCH 01/10] scsi: bsg: Don't copy sense data to user memory when canceled James Houghton
2026-10-26 22:17   ` sashiko-bot
2026-10-27  2:41   ` Jens Axboe
2026-10-27 17:52     ` James Houghton
2026-10-26 21:52 ` [RFC PATCH 02/10] btrfs: Don't copy encoded read " James Houghton
2026-10-26 22:06   ` sashiko-bot
2026-10-27  2:42   ` Jens Axboe
2026-10-26 21:52 ` [RFC PATCH 03/10] bpf: Fail sleepable user copy helpers when current->mm is NULL James Houghton
2026-10-26 21:59   ` sashiko-bot
2026-10-26 22:30   ` bot+bpf-ci
2026-10-26 22:30     ` bot+bpf-ci
2026-10-27 18:50     ` James Houghton
2026-10-26 21:52 ` [RFC PATCH 04/10] stacktrace: Don't unwind the user stack without an mm James Houghton
2026-10-26 21:59   ` sashiko-bot
2026-10-26 22:30   ` bot+bpf-ci
2026-10-26 22:30     ` bot+bpf-ci
2026-10-26 22:55     ` James Houghton
2026-10-26 21:52 ` [RFC PATCH 05/10] perf/core: " James Houghton
2026-10-26 21:58   ` sashiko-bot
2026-10-27 11:09   ` Peter Zijlstra
2026-10-27 17:45     ` James Houghton
2026-10-26 21:52 ` [RFC PATCH 06/10] uaccess: Refuse and warn on user copies when current->mm is NULL James Houghton
2026-10-26 22:08   ` sashiko-bot
2026-10-26 22:42   ` bot+bpf-ci
2026-10-26 22:42     ` bot+bpf-ci
2026-10-26 23:41     ` James Houghton
2026-10-26 21:52 ` [RFC PATCH 07/10] uaccess: Fail user nofault helpers quietly " James Houghton
2026-10-26 22:11   ` sashiko-bot [this message]
2026-10-26 21:52 ` [RFC PATCH 08/10] uaccess: Refuse and warn on __copy_from_user_inatomic() without an mm James Houghton
2026-10-26 22:05   ` sashiko-bot
2026-10-26 22:30   ` bot+bpf-ci
2026-10-26 22:30     ` bot+bpf-ci
2026-10-26 22:41     ` James Houghton
2026-10-26 21:52 ` [RFC PATCH 09/10] uaccess: Refuse and warn on more user accesses " James Houghton
2026-10-26 22:00   ` sashiko-bot
2026-10-26 21:52 ` [RFC PATCH 10/10] uaccess: Move the NULL mm warning out of line James Houghton
2026-10-26 22:02   ` sashiko-bot
2026-10-26 23:02   ` Arnd Bergmann
2026-10-26 23:51     ` James Houghton
2026-10-27  0:12 ` [RFC PATCH 00/10] uaccess: Refuse and warn on user accesses when current->mm is NULL Arnd Bergmann
2026-10-27 10:33   ` Arnd Bergmann
2026-10-27 17:29   ` James Houghton
2026-10-27 18:32     ` Arnd Bergmann
2026-10-27 21:18       ` Sean Christopherson
2026-10-27 23:17       ` James Houghton
2026-10-28 23:13         ` Arnd Bergmann

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=sashiko-outbox-185785@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=jthoughton@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.