linux-kernel - Re: Re: [PATCH -tip/x86/jumplabel] x86: call out into int3 handler directly instead of using notifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Jul 2013 09:45:05 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Jiri Kosina <jkosina@...e.cz>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	linux-kernel@...r.kernel.org,
	Fengguang Wu <fengguang.wu@...el.com>,
	Steven Rostedt <rostedt@...dmis.org>, x86@...nel.org
Subject: Re: Re: [PATCH -tip/x86/jumplabel] x86: call out into int3 handler
 directly instead of using notifier


* Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:

> (2013/07/23 6:00), Jiri Kosina wrote:
> > On Mon, 22 Jul 2013, H. Peter Anvin wrote:
> > 
> >>  What is the baseline for this patch?
> > 
> > Hi!
> > 
> > it's x86/jumplabel branch, as a followup to commit 
> > fd4363fff3d96 ("x86: Introduce int3 (breakpoint)-based instruction 
> > patching") sitting there.
> 
> AFAICS, tip/master already merged Jiri's works on tip/x86/jumplabel.
> Thus both branches need this. (especially, since this is actual
> bugfix, it should go into tip/master.)

I resolved it yesterday by keeping the kprobes patches in perf/core - just 
forgot to push it all out.

I've pushed it out now, so perf/core should be a baseline: it merges in 
x86/jumplabel and then applies the kprobes patches (historically in 
perf/core).

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/