From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Jordan Rife <jrife@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Alexei Starovoitov <ast@kernel.org>, bpf <bpf@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
LKML <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Michael Jeanson <mjeanson@efficios.com>,
Namhyung Kim <namhyung@kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
syzbot+b390c8062d8387b6272a@syzkaller.appspotmail.com,
Yonghong Song <yhs@fb.com>
Subject: Re: [RFC PATCH] tracing: Fix syscall tracepoint use-after-free
Date: Thu, 24 Oct 2024 14:18:08 -0400 [thread overview]
Message-ID: <d3ce751e-e694-4b1d-9503-7e46e28eecf4@efficios.com> (raw)
In-Reply-To: <CAEf4Bzb4ywpMxchWcMfW9Lzh=re4x1zbMfz2aPRiUa29nUMB=g@mail.gmail.com>
On 2024-10-24 13:12, Andrii Nakryiko wrote:
[...]
> And as Alexei asked, where are the applied
> patches adding faultable tracepoints?
>
On linux-next next-20241024 :
0850e1bc88b1 tracing/bpf: Add might_fault check to syscall probes
cdb537ac4179 tracing/perf: Add might_fault check to syscall probes
a3204c740a59 tracing/ftrace: Add might_fault check to syscall probes
a363d27cdbc2 tracing: Allow system call tracepoints to handle page faults <---- This is where bisection points as first offending commit.
4aadde89d81f tracing/bpf: disable preemption in syscall probe
65e7462a16ce tracing/perf: disable preemption in syscall probe
13d750c2c03e tracing/ftrace: disable preemption in syscall probe
0e6caab8db8b tracing: Declare system call tracepoints with TRACE_EVENT_SYSCALL
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2024-10-24 18:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 15:18 [RFC PATCH] tracing: Fix syscall tracepoint use-after-free Mathieu Desnoyers
2024-10-22 16:14 ` Jordan Rife
2024-10-22 17:54 ` Mathieu Desnoyers
2024-10-22 19:53 ` Andrii Nakryiko
2024-10-22 20:04 ` Mathieu Desnoyers
2024-10-23 0:20 ` Steven Rostedt
2024-10-23 1:11 ` Mathieu Desnoyers
2024-10-23 1:24 ` Jordan Rife
2024-10-23 14:56 ` Jordan Rife
2024-10-23 15:13 ` Mathieu Desnoyers
2024-10-24 0:40 ` Steven Rostedt
2024-10-23 15:14 ` Alexei Starovoitov
2024-10-23 15:19 ` Mathieu Desnoyers
2024-10-24 1:28 ` Alexei Starovoitov
2024-10-24 2:05 ` Steven Rostedt
2024-10-24 17:12 ` Jordan Rife
2024-10-24 17:12 ` Andrii Nakryiko
2024-10-24 17:50 ` Jordan Rife
2024-10-24 18:18 ` Mathieu Desnoyers [this message]
2024-10-25 15:01 ` Jordan Rife
2024-10-25 20:19 ` Andrii Nakryiko
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=d3ce751e-e694-4b1d-9503-7e46e28eecf4@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=joel@joelfernandes.org \
--cc=jrife@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mjeanson@efficios.com \
--cc=namhyung@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzbot+b390c8062d8387b6272a@syzkaller.appspotmail.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox