linux-kernel - Re: perf: report loops endlessly if record was killed via SIGTERM

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: <517E5905.1070700@gmail.com>
Date:	Mon, 29 Apr 2013 07:27:01 -0400
From:	David Ahern <dsahern@...il.com>
To:	Mike Galbraith <bitbucket@...ine.de>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: perf: report loops endlessly if record was killed via SIGTERM

On 4/29/13 4:00 AM, Mike Galbraith wrote:
> Say SIGINT instead,
> and it works as expected.  SIGTERM leaves perf.data in a bad state that
> report can't deal with, but it'll happily keep trying forever.

header is usually updated on_exit which requires a clean exit. perhaps 
we should add SIGTERM to the signal list.

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