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] [day] [month] [year] [list]

Message-ID: <1367235801.4656.66.camel@marge.simpson.net>
Date:	Mon, 29 Apr 2013 13:43:21 +0200
From:	Mike Galbraith <bitbucket@...ine.de>
To:	David Ahern <dsahern@...il.com>
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 Mon, 2013-04-29 at 07:27 -0400, David Ahern wrote: 
> 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.

Yeah.  Graceful exit, and idiot proofing for free :)

-Mike

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