All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: x86@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@kernel.org>,
	Suleiman Souhlal <suleiman@google.com>, bpf <bpf@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Nadav Amit <namit@vmware.com>
Subject: Re: [PATCH -tip v4 0/2] x86/kprobes: Fix to check not-kprobe's int3 correctly
Date: Mon, 19 Dec 2022 16:23:23 +0100	[thread overview]
Message-ID: <Y6CB698Owg87wIbs@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <167146050052.1374301.10407562178447545337.stgit@devnote3>

On Mon, Dec 19, 2022 at 11:35:00PM +0900, Masami Hiramatsu (Google) wrote:
> Masami Hiramatsu (Google) (2):
>       x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK
>       x86/kprobes: Fix optprobe optimization check with CONFIG_RETHUNK
> 

Thanks, I'll go queue these in x86/urgent after -rc1 happens.

      parent reply	other threads:[~2022-12-19 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:35 [PATCH -tip v4 0/2] x86/kprobes: Fix to check not-kprobe's int3 correctly Masami Hiramatsu (Google)
2022-12-19 14:35 ` [PATCH -tip v4 1/2] x86/kprobes: Fix kprobes instruction boudary check with CONFIG_RETHUNK Masami Hiramatsu (Google)
2022-12-27 11:59   ` [tip: x86/urgent] " tip-bot2 for Masami Hiramatsu (Google)
2022-12-19 14:35 ` [PATCH -tip v4 2/2] x86/kprobes: Fix optprobe optimization " Masami Hiramatsu (Google)
2022-12-27 11:59   ` [tip: x86/urgent] " tip-bot2 for Masami Hiramatsu (Google)
2022-12-19 15:23 ` Peter Zijlstra [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=Y6CB698Owg87wIbs@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@suse.de \
    --cc=bpf@vger.kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namit@vmware.com \
    --cc=rostedt@goodmis.org \
    --cc=suleiman@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.