From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Michael Jeanson <mjeanson@efficios.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Alexei Starovoitov <ast@kernel.org>, Yonghong Song <yhs@fb.com>,
"Paul E . McKenney" <paulmck@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
bpf@vger.kernel.org, Joel Fernandes <joel@joelfernandes.org>,
Jordan Rife <jrife@google.com>
Subject: Re: [PATCH v5 0/4] Faultable syscall tracepoints updates
Date: Wed, 30 Oct 2024 19:33:18 -0400 [thread overview]
Message-ID: <20241030193318.712118cf@rorschach.local.home> (raw)
In-Reply-To: <20241030144634.721630-1-mathieu.desnoyers@efficios.com>
On Wed, 30 Oct 2024 10:46:30 -0400
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> This series addresses use-after-free of faultable syscall tracepoints
> reported by test bots using Syzkaller.
>
> This applies on linux-next 20241022.
Please Cc, linux-trace-kernel@vger.kernel.org so that your patches
appear in patchwork. Otherwise they will not be seen. I can pull them
from my "INBOX patchwork" but that is outside the workflow of the
tracing subsystem.
-- Steve
prev parent reply other threads:[~2024-10-30 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 14:46 Mathieu Desnoyers
2024-10-30 14:46 ` [PATCH v5 1/4] tracing: Introduce tracepoint extended structure Mathieu Desnoyers
2024-10-30 14:46 ` [PATCH v5 2/4] tracing: Introduce tracepoint_is_faultable() Mathieu Desnoyers
2024-10-30 14:46 ` [PATCH v5 3/4] tracing: Fix syscall tracepoint use-after-free Mathieu Desnoyers
2024-10-30 14:46 ` [PATCH v5 4/4] tracing: Add might_fault() check in __DECLARE_TRACE_SYSCALL Mathieu Desnoyers
2024-10-30 23:33 ` Steven Rostedt [this message]
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=20241030193318.712118cf@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.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=mathieu.desnoyers@efficios.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=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®