From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Yang Jihong <yangjihong1@huawei.com>
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>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] kprobes: Fix issues related to optkprobe
Date: Thu, 16 Feb 2023 23:12:44 +0900 [thread overview]
Message-ID: <20230216231244.54e18b8a8656338eeb43b8cb@kernel.org> (raw)
In-Reply-To: <20230216034247.32348-1-yangjihong1@huawei.com>
On Thu, 16 Feb 2023 11:42:45 +0800
Yang Jihong <yangjihong1@huawei.com> wrote:
> Fixed optkprobe issues, mainly related to the x86 architecture.
>
> Yang Jihong (2):
> x86/kprobes: Fix __recover_optprobed_insn check optimizing logic
> x86/kprobes: Fix arch_check_optimized_kprobe check within
> optimized_kprobe range
>
> arch/x86/kernel/kprobes/opt.c | 6 +++---
> include/linux/kprobes.h | 2 ++
> kernel/kprobes.c | 4 ++--
> 3 files changed, 7 insertions(+), 5 deletions(-)
Thanks for updating! These look good to me!
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you,
>
> --
>
> Changes since v1:
> - Remove patch1 since there is already a fix patch.
> - Add "cc stable" and modify comment for patch2.
> - Use "kprobe_disarmed" instead of "kprobe_disabled" for patch3.
> - Add fix commmit and "cc stable" for patch3.
>
> 2.30.GIT
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-02-16 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 3:42 [PATCH v2 0/2] kprobes: Fix issues related to optkprobe Yang Jihong
2023-02-16 3:42 ` [PATCH v2 1/2] x86/kprobes: Fix __recover_optprobed_insn check optimizing logic Yang Jihong
2023-02-16 3:42 ` [PATCH v2 2/2] x86/kprobes: Fix arch_check_optimized_kprobe check within optimized_kprobe range Yang Jihong
2023-02-16 14:12 ` Masami Hiramatsu [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=20230216231244.54e18b8a8656338eeb43b8cb@kernel.org \
--to=mhiramat@kernel.org \
--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=mingo@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yangjihong1@huawei.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