linux-kernel - Re: [discuss] BTS overflow handling, was: [PATCH] perf_counter: Fix a race on perf_counter

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, 1 Sep 2009 15:09:42 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	"Metzger, Markus T" <markus.t.metzger@...el.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"hpa@...or.com" <hpa@...or.com>,
	"markus.t.metzger@...il.com" <markus.t.metzger@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [discuss] BTS overflow handling, was: [PATCH] perf_counter:
	Fix a race on perf_counter_ctx


* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> > In any case, this is getting late for the upcoming merge window. 
> > Would you rather drop the BTS patch or disable kernel tracing?
> 
> I don't think we need to drop it, at worst we could defer the 
> patch to .33, but I think we can indeed get away with disabling 
> the kernel tracing for now.

That could be done via a simple patch that does not enable BTS 
tracing if the .kernel attribute bit is set. I.e. we enable BTS on a 
narrower set of config settings than in the past - but still keep 
the code largely untouched.

	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/