[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190222122336.GD3940@krava>
Date: Fri, 22 Feb 2019 13:23:36 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Jiri Olsa <jolsa@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Adrian Hunter <adrian.hunter@...el.com>,
Stephane Eranian <eranian@...gle.com>,
Alexey Budankov <alexey.budankov@...ux.intel.com>
Subject: Re: [PATCH 04/17] perf data: Fail check_backup in case of error
On Thu, Feb 21, 2019 at 02:23:30PM -0800, Andi Kleen wrote:
> On Thu, Feb 21, 2019 at 10:41:32AM +0100, Jiri Olsa wrote:
> > And display the error message from removing
> > the old data file:
> >
> > $ perf record ls
> > Can't remove old data: Permission denied (perf.data.old)
> > Perf session creation failed.
> >
> > Not sure how to make fail the rename (after we successfully
> > remove the destination file/dir) to show the message,
> > anyway let's have it there.
>
> The use of rm_rf is really scary. So I simple command line typo could turn
> this into rm -rf / ?
>
> Please add some sanity checks to not remove multiple levels,
> and only remove files which look like they are generated
> by perf.
right, will do
jirka
Powered by blists - more mailing lists