[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140429113304.GA13658@twins.programming.kicks-ass.net>
Date: Tue, 29 Apr 2014 13:33:04 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Stephane Eranian <eranian@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Namhyung Kim <namhyung.kim@....com>
Subject: Re: [PATCH v3 2/3] perf record: Propagate exit status of a command
line workload
On Tue, Apr 29, 2014 at 01:19:39PM +0200, Peter Zijlstra wrote:
> On Tue, Apr 29, 2014 at 12:56:54PM +0200, Jiri Olsa wrote:
> >
> > perf_counter tools: Propagate signals properly
> > commit f7b7c26e01e51fe46097e11f179dc71ce7950084
> > Author: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> > Date: Wed Jun 10 15:55:59 2009 +0200
> >
> > but I dont think we need to do that
>
> But but but, then you're re-introducing that fail again? That no good.
The thing is, just the return value is not sufficient to determine if
the child was interrupted.
See WAIT(2), things like WIFSIGNALED() will not work when you just
propagate the return value, you need to terminate the task with a
signal to propagate this.
--
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/
Powered by blists - more mailing lists