From: Yang Jihong <yangjihong1@huawei.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<naveen.n.rao@linux.ibm.com>, <anil.s.keshavamurthy@intel.com>,
<davem@davemloft.net>, <ast@kernel.org>, <peterz@infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] kprobes: Fixed probe nodes not correctly removed when forcibly unoptimized
Date: Thu, 16 Feb 2023 10:52:00 +0800 [thread overview]
Message-ID: <94ffd94f-23b6-8d11-43c5-cd5ff16cac65@huawei.com> (raw)
In-Reply-To: <20230215235517.800c5089318b5353e7304b67@kernel.org>
Hello Masami,
On 2023/2/15 22:55, Masami Hiramatsu (Google) wrote:
> Hi Yang,
>
> Thanks for reporting, but maybe this is a part of following fix.
>
> https://lore.kernel.org/all/167448024501.3253718.13037333683110512967.stgit@devnote3/
>
> Can you confirm that fixes the same issue?
Yes, I've tested and confirmed that the patch you mentioned above fixes
the same issue.
Will remove it in next version.
Thanks
Yang.
next prev parent reply other threads:[~2023-02-16 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 11:54 [PATCH 0/3] kprobes: Fix issues related to optkprobe Yang Jihong
2023-02-15 11:54 ` [PATCH 1/3] kprobes: Fixed probe nodes not correctly removed when forcibly unoptimized Yang Jihong
2023-02-15 14:55 ` Masami Hiramatsu
2023-02-16 2:52 ` Yang Jihong [this message]
2023-02-15 11:54 ` [PATCH 2/3] x86/kprobes: Fix __recover_optprobed_insn check optimizing logic Yang Jihong
2023-02-15 15:08 ` Masami Hiramatsu
2023-02-16 2:53 ` Yang Jihong
2023-02-15 11:54 ` [PATCH 3/3] x86/kprobes: Fix arch_check_optimized_kprobe check within optimized_kprobe range Yang Jihong
2023-02-15 15:48 ` Masami Hiramatsu
2023-02-16 2:56 ` Yang Jihong
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=94ffd94f-23b6-8d11-43c5-cd5ff16cac65@huawei.com \
--to=yangjihong1@huawei.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®