mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinke Han <jinkehan@didiglobal.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <tglx@kernel.org>,
	<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
	<x86@kernel.org>, <hpa@zytor.com>, <nik.borisov@suse.com>,
	<rppt@kernel.org>, <peterz@infradead.org>, <mhiramat@redhat.com>
Subject: Re: [PATCH] x86/kprobes: Fix boundary check in insn_jump_into_range()
Date: Fri, 20 Nov 2026 10:23:35 +0800	[thread overview]
Message-ID: <20261120022335.GA1970@didi-ThinkCentre-M920t-N000> (raw)
In-Reply-To: <b136b9da-7089-4232-ad96-6174a48844d9@intel.com>

> On Thu, Nov 19, 2026 at 04:41:04PM -0800, Dave Hansen wrote:
> > On 11/19/26 16:36, Jinke Han wrote:
> >> Since there is no reported failure, I'm fine with dropping the Fixes:
> >> tag if you'd prefer to treat this as a cleanup. I can also post a
> >> separate change that makes the check use the actual optimized length
> >> instead of the open-coded DISP32_SIZE, if you think that's the better
> >> direction, and add a regression case under
> >> tools/testing/selftests/kprobes.
> > 
> > The Fixes: is fine, but it would be nice to have a better changelog
> > about what's going on.
> > 
> > Not voluminous, just better, please.

I'll send a v2 to improve the changelog.

Thanks,
Jinke Han

      reply	other threads:[~2026-11-20  2:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 12:25 Jinke Han
2026-11-19 19:41 ` Dave Hansen
2026-11-20  0:36   ` Jinke Han
2026-11-20  0:41     ` Dave Hansen
2026-11-20  2:23       ` Jinke Han [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=20261120022335.GA1970@didi-ThinkCentre-M920t-N000 \
    --to=jinkehan@didiglobal.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=peterz@infradead.org \
    --cc=rppt@kernel.org \
    --cc=tglx@kernel.org \
    --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®