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] [day] [month] [year] [list]
Message-ID: <51F63487.7040003@zytor.com>
Date:	Mon, 29 Jul 2013 02:23:19 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	"H. Peter Anvin" <hpa@...ux.intel.com>, mingo@...nel.org,
	linux-kernel@...r.kernel.org, masami.hiramatsu.pt@...achi.com,
	rostedt@...dmis.org, tglx@...utronix.de, fengguang.wu@...el.com,
	tip-bot for Jiri Kosina <tipbot@...or.com>,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] kprobes/x86: Call out into INT3 handler directly
 instead of using notifier

On 07/29/2013 02:18 AM, Jiri Kosina wrote:
> On Mon, 29 Jul 2013, H. Peter Anvin wrote:
> 
>>>> Please note that putting this patch in perf/core means x86/jumplabel is
>>>> completely nonfunctional by itself.
>>>
>>> I'd like to point out that this is still the case ... TIA,
>>
>> What is?
> 
> 17f41571bb2c4a is only in perf/core, x86/jumplabel is missing it. I am not 
> sure about the tip workflow, but as it is now, x86/jumplabel is buggy, so 
> it should be either fixed (by pulling 17f41571bb2c4a from perf/core) or 
> removed, or somehow marked as broken ... ?
> 
> Not a big deal for me as long as perf/core is fine, but as you were 
> mentioning it ...
> 

Yes, we know.  In effect, x86/jumplabel not really a working standalone
topic branch at the moment.  It is probably not worth fixing it for this
kernel cycle, as the number of patches involved is relatively small, but
it is perhaps a bit unfortunate.

	-hpa


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ