From: Adam Zabrocki <pi3@pi3.com.pl>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, Solar Designer <solar@openwall.com>
Subject: Re: [PATCH] x86/kprobes: Fix KRETPROBES when CONFIG_KRETPROBE_ON_RETHOOK is set
Date: Fri, 22 Apr 2022 18:35:27 +0200 [thread overview]
Message-ID: <20220422163527.GA7810@pi3.com.pl> (raw)
In-Reply-To: <20220422235401.a3ece3ed2b008dc790cdb6e2@kernel.org>
Sure, I will do it.
Thanks for help,
Adam
On Fri, Apr 22, 2022 at 11:54:01PM +0900, Masami Hiramatsu wrote:
> On Fri, 22 Apr 2022 09:43:50 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Fri, 22 Apr 2022 22:05:23 +0900
> > Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > > Hi Steve,
> > >
> > > Can you pick this fix to urgent branch? Or Should I ask bpf people?
> >
> > It looks to fix a bug from a commit pulled in from the BPF folks. I would
> > have them take it.
>
> OK, thanks!
>
> Adam, can you resend your patch with my Ack and modify the PATCH tag as
> "[PATCH bpf]", to "Alexei Starovoitov <ast@kernel.org>", "Andrii Nakryiko <andrii@kernel.org>",
> and Cc: "bpf@vger.kernel.org" ?
>
> Thank you,
>
> >
> > Thanks,
> >
> > -- Steve
> > >
> > > > Fixes: 73f9b911faa7 ("kprobes: Use rethook for kretprobe if possible")
>
>
> --
> Masami Hiramatsu <mhiramat@kernel.org>
--
pi3 (pi3ki31ny) - pi3 (at) itsec pl
http://pi3.com.pl
prev parent reply other threads:[~2022-04-22 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 18:07 KRETPROBES are broken since the commit 73f9b911faa7 Adam Zabrocki
2022-04-15 18:10 ` [PATCH] x86/kprobes: Fix KRETPROBES when CONFIG_KRETPROBE_ON_RETHOOK is set Adam Zabrocki
2022-04-16 14:06 ` Masami Hiramatsu
2022-04-22 13:05 ` Masami Hiramatsu
2022-04-22 13:43 ` Steven Rostedt
2022-04-22 14:54 ` Masami Hiramatsu
2022-04-22 16:35 ` Adam Zabrocki [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=20220422163527.GA7810@pi3.com.pl \
--to=pi3@pi3.com.pl \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=rostedt@goodmis.org \
--cc=solar@openwall.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