From: Steven Rostedt <rostedt@goodmis.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>, bpf <bpf@vger.kernel.org>,
linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Yonghong Song <yhs@fb.com>,
Song Liu <songliubraving@fb.com>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCHv3 0/4] x86/fgraph,bpf: Fix ORC stack unwind from return probe
Date: Wed, 5 Nov 2025 10:03:59 -0500 [thread overview]
Message-ID: <20251105100359.2e6eeae5@gandalf.local.home> (raw)
In-Reply-To: <CAADnVQJRv+2NT2TGd7nXbOtx_Cnsg=kOJuikOtL9aEdUVmwvag@mail.gmail.com>
On Tue, 4 Nov 2025 18:20:41 -0800
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> Steven, Peter,
>
> How should we route this?
>
> If you take it into your tree, please send it to Linus right away,
> so we can pull it into bpf/bpf-next trees.
> The conflicts in selftests/bpf in the last merge window
> were annoying. I don't want to see a repeat.
Let me run this through my tests and then I'll give you an Acked-by and you
can take it through your tree.
-- Steve
next prev parent reply other threads:[~2025-11-05 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 21:54 [PATCHv3 0/4] x86/fgraph,bpf: Fix ORC stack unwind from return probe Jiri Olsa
2025-11-04 21:54 ` [PATCHv3 1/4] Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()" Jiri Olsa
2025-11-04 21:54 ` [PATCHv3 2/4] x86/fgraph,bpf: Fix stack ORC unwind from kprobe_multi return probe Jiri Olsa
2025-11-04 21:54 ` [PATCHv3 3/4] selftests/bpf: Add stacktrace ips test for kprobe_multi/kretprobe_multi Jiri Olsa
2025-11-04 21:54 ` [PATCHv3 4/4] selftests/bpf: Add stacktrace ips test for raw_tp Jiri Olsa
2025-11-05 2:20 ` [PATCHv3 0/4] x86/fgraph,bpf: Fix ORC stack unwind from return probe Alexei Starovoitov
2025-11-05 15:03 ` Steven Rostedt [this message]
2025-11-05 23:04 ` Steven Rostedt
2025-11-06 1:15 ` Alexei Starovoitov
2025-11-06 1:20 ` patchwork-bot+netdevbpf
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=20251105100359.2e6eeae5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=x86@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).