From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Beau Belgrave <beaub@linux.microsoft.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-trace-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, bpf <bpf@vger.kernel.org>,
David Vernet <void@manifault.com>,
dthaler@microsoft.com, brauner@kernel.org, hch@infradead.org
Subject: Re: [PATCH] tracing/user_events: Run BPF program if attached
Date: Tue, 16 May 2023 22:29:19 -0400 [thread overview]
Message-ID: <20230516222919.79bba667@rorschach.local.home> (raw)
In-Reply-To: <CAHk-=wj1hh=ZUriY9pVFvD1MjqbRuzHc4yz=S2PCW7u3W0-_BQ@mail.gmail.com>
On Tue, 16 May 2023 18:46:29 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> So don't even ask for other GUP functionality, much less the "remote"
> kind. Not going to happen. If you think you need access to remote
> process memory, you had better do it in process context, or you had
> better just think again.
So this code path is very much in user context (called directly by a
write system call). The issue that Alexei had was that it's also in an
rcu_read_lock() section.
I wonder if this all goes away if we switch to SRCU? That is, sleepable RCU.
-- Steve
next prev parent reply other threads:[~2023-05-17 2:29 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:37 [PATCH] tracing/user_events: Run BPF program if attached Beau Belgrave
2023-05-09 15:24 ` Alexei Starovoitov
2023-05-09 17:01 ` Steven Rostedt
2023-05-09 20:30 ` Steven Rostedt
2023-05-09 20:42 ` Steven Rostedt
2023-05-15 16:57 ` Alexei Starovoitov
2023-05-15 18:33 ` Steven Rostedt
2023-05-15 19:35 ` Beau Belgrave
2023-05-15 21:38 ` Steven Rostedt
2023-05-15 19:24 ` Beau Belgrave
2023-05-15 21:57 ` Steven Rostedt
2023-05-17 0:36 ` Alexei Starovoitov
2023-05-17 0:56 ` Linus Torvalds
2023-05-17 1:46 ` Linus Torvalds
2023-05-17 2:29 ` Steven Rostedt [this message]
2023-05-17 3:03 ` Linus Torvalds
2023-05-17 17:22 ` Beau Belgrave
2023-05-17 18:15 ` Linus Torvalds
2023-05-17 19:07 ` Beau Belgrave
2023-05-17 19:26 ` Linus Torvalds
2023-05-17 19:36 ` Beau Belgrave
2023-05-17 19:36 ` Linus Torvalds
2023-05-17 19:37 ` Linus Torvalds
2023-05-17 23:00 ` Beau Belgrave
2023-05-17 23:14 ` Linus Torvalds
2023-05-17 23:25 ` Steven Rostedt
2023-05-18 0:14 ` Beau Belgrave
2023-05-18 0:23 ` Linus Torvalds
2023-05-17 20:08 ` Linus Torvalds
2023-05-17 1:26 ` Steven Rostedt
2023-05-17 16:50 ` Beau Belgrave
2023-05-18 0:10 ` Alexei Starovoitov
2023-05-18 0:19 ` Beau Belgrave
2023-05-18 0:56 ` Alexei Starovoitov
2023-05-18 1:18 ` Beau Belgrave
2023-05-18 2:08 ` Steven Rostedt
2023-05-18 3:14 ` Alexei Starovoitov
2023-05-18 13:36 ` Steven Rostedt
2023-05-18 17:28 ` Beau Belgrave
2023-06-01 9:46 ` Christian Brauner
2023-06-01 15:24 ` Beau Belgrave
2023-06-01 15:57 ` Christian Brauner
2023-06-01 16:29 ` Beau Belgrave
2023-06-06 13:37 ` Masami Hiramatsu
2023-06-06 17:05 ` Beau Belgrave
2023-06-07 14:07 ` Masami Hiramatsu
2023-06-07 19:26 ` Beau Belgrave
2023-06-08 0:25 ` Masami Hiramatsu
2023-05-17 17:51 ` Beau Belgrave
2023-06-06 13:57 ` Masami Hiramatsu
2023-06-06 16:57 ` Andrii Nakryiko
2023-06-06 20:57 ` Beau Belgrave
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=20230516222919.79bba667@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dthaler@microsoft.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=void@manifault.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.