linux-kernel - Re: [PATCH] event: fix TP_printk() argument in sched

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]

Message-ID: <1320279201.4793.58.camel@gandalf.stny.rr.com>
Date:	Wed, 02 Nov 2011 20:13:21 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	David Ahern <dsahern@...il.com>
Cc:	Andrew Vagin <avagin@...nvz.org>, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>, devel@...nvz.org,
	Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: [PATCH] event: fix TP_printk() argument in sched_switch

On Wed, 2011-11-02 at 17:23 -0600, David Ahern wrote:
> On 11/02/2011 05:07 PM, Steven Rostedt wrote:
> > This is a perf userspace bug, not a kernel one. Please fix the userspace
> > tool instead.
> > 
> > Note, the new version of libparsevent handles this case without issue.
> > Perf just needs to be updated.
> 
> I dare ask..... has any progress been made on that front? ie., with
> respect to lib names and locations within the tools dir.
> 

You dare too much... going into dangerous territory ;)


No, unfortunately, no progress has been made. I spoke a little with Ingo
in Prague, with Arjan too, and we still seem to disagree how to go
forward with this.

I may just punt and start pushing a separate library as it is today.
That is, a separate package, outside the kernel proper.

-- Steve


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