linux-kernel - Re: [PATCH] perf/trace: use read() instead of lseek() in trace_event

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: <20100514162222.GB5504@nowhere>
Date:	Fri, 14 May 2010 18:22:26 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Borislav Petkov <bp@...64.org>
Cc:	Tom Zanussi <tzanussi@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf/trace: use read() instead of lseek() in
	trace_event_read.c:skip()

On Fri, May 14, 2010 at 06:12:55PM +0200, Borislav Petkov wrote:
> From: Tom Zanussi <tzanussi@...il.com>
> Date: Tue, May 04, 2010 at 11:02:10PM -0500
> 
> Hi,
> 
> > Here's a small fix for a problem affecting live-mode, introduced in the
> > past day or so:
> > 
> > root@...picana:~# perf trace rwtop
> > perf trace started with Perl
> > script /root/libexec/perf-core/scripts/perl/rwtop.pl
> > 
> >   Fatal: did not read header event
> > 
> > commit d00a47cce569a3e660a8c9de5d57af28d6a9f0f7 added a skip()
> > function to skip over e.g. header_page, but this doesn't work for live
> > mode.  This patch re-implements skip() to use read() instead of
> > lseek() to fix that.
> > 
> > Signed-off-by: Tom Zanussi <tzanussi@...il.com>
> 
> has this one landed in any tree in the meantime?
> 
> tip/perf/core doesn't have it.


I forgot to queue it, my bad.

Queued, thanks.

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