[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130603134925.GA13548@krava.brq.redhat.com>
Date:	Mon, 3 Jun 2013 15:49:25 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Robert Richter <rric@...nel.org>
Cc:	Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel@...r.kernel.org,
	Robert Richter <robert.richter@...xeda.com>
Subject: Re: [PATCH 16/16] perf, persistent: Allow multiple users for an event
On Fri, May 31, 2013 at 10:47:36AM +0200, Robert Richter wrote:
> From: Robert Richter <robert.richter@...xeda.com>
SNIP
>  out:
>  	mutex_unlock(&per_cpu(pers_events_lock, cpu));
>  }
> @@ -182,18 +195,31 @@ fail:
>  int perf_get_persistent_event_fd(unsigned cpu, struct perf_event_attr *attr)
>  {
>  	struct pers_event_desc *desc;
> +	struct perf_event *event;
>  	int event_fd = -ENODEV;
>  
>  	mutex_lock(&per_cpu(pers_events_lock, cpu));
maybe check for valid cpu, since perf_get_persistent_event_fd is
called directly from syscall allowing anything in cpu
(unrelated to this patch, but I couldn't find the original
patch that adds perf_get_persistent_event_fd)
jirka
--
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