From: Jinke Han <jinkehan@didiglobal.com>
To: <mhiramat@kernel.org>
Cc: <tglx@kernel.org>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<laoar.shao@gmail.com>, <peterz@infradead.org>, <jgross@suse.com>,
<kees@kernel.org>, <jpoimboe@kernel.org>, <rppt@kernel.org>,
<sohil.mehta@intel.com>, <linusw@kernel.org>,
<linux-kernel@vger.kernel.org>, <tiozhang@didiglobal.com>
Subject: Re: [PATCH v2] x86/kprobe: Fix crash when probe cs call
Date: Tue, 8 Sep 2026 13:00:09 +0800 [thread overview]
Message-ID: <20260908050009.GA11579@didi-ThinkCentre-M920t-N000> (raw)
> Thanks for fixing! I have just one comment here;
> [...]
> > @@ -2180,8 +2181,14 @@ int3_exception_notify(struct notifier_block *self, unsigned long val, void *data
> >
> > if (regs->ip - INT3_INSN_SIZE != selftest)
> > return NOTIFY_DONE;
> > -
> > - int3_emulate_call(regs, (unsigned long)&int3_selftest_callee);
> > + /*
> > + * As seen in int3_selftest_asm, the effective return address
> > + * should be placed immediately after the instruction sequence
> > + * [int3; nop; nop; nop; nop.]. Therefore, CALL_INSN_SIZE works
> > + * perfectly well here.
> Nit: This explanation is somewhat wrong. alternatives only support 5-byte
> call. The TEXT_POKE_MAX_OPCODE_SIZE is 5. When len == 6, alternative.c
> explicitly reserves this only for 0x0f prefixed Jcc.d32
> See alternative.c
> > /*
> > * NOTE: crazy scheme to allow patching Jcc.d32 but not increase the size of
> > * this thing. When len == 6 everything is prefixed with 0x0f and we map
> * opcode to Jcc.d8, using len to distinguish.
> > */
> So we don't need to take care of 6 bytes call here.
Thanks for the correction! I'll fix it in v3 soon.
--
Jinke Han
> Others looks good to me.
> Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> BTW, can this be picked via tip tree ? or I can pick it.
> Thank you,
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2026-09-08 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 5:00 Jinke Han [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-07 19:24 Jinke Han
2026-09-08 1:44 ` Masami Hiramatsu
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=20260908050009.GA11579@didi-ThinkCentre-M920t-N000 \
--to=jinkehan@didiglobal.com \
--cc=20260908104425.98040997699efaa2bc741e0b@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=tiozhang@didiglobal.com \
--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®