linux-kernel - Re: [PATCH v4 0/4] perf timechart io mode

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: <20140625112019.GC21788@stfomichev-desktop.yandex.net>
Date:	Wed, 25 Jun 2014 15:20:19 +0400
From:	Stanislav Fomichev <stfomichev@...dex-team.ru>
To:	David Ahern <dsahern@...il.com>
Cc:	Jiri Olsa <jolsa@...hat.com>, linux-kernel@...r.kernel.org,
	a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...hat.com,
	acme@...nel.org, namhyung@...nel.org, artagnon@...il.com,
	rusty@...tcorp.com.au, bp@...e.de
Subject: Re: [PATCH v4 0/4] perf timechart io mode

> >maybe we dont need to fail in this case.. seems like it should
> >not be hard to detect, wanr and recover? ;-)
The easiest way is just to bail out and don't try to be smart, that's
what I do now.

Another approach would be to just convert all my consistency
checks to warnings and skip invalid events (and hope it somehow works). I
think it makes sense when for some reason we have perf.data which
is not really consistent but we still want to get something out of it.

> seems to me it should not be happening at all. It seems like the head caught
> the tail and was not properly detected.
So you mean it perf record's fault?
--
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/