public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@elte.hu, ak@linux.intel.com, kan.liang@intel.com,
	acme@redhat.com
Subject: Re: [PATCH] perf/core: fix perf_proc_update_handler() bug
Date: Fri, 18 Jan 2019 10:52:51 +0100	[thread overview]
Message-ID: <20190118095251.GB28346@krava> (raw)
In-Reply-To: <1547169436-6266-1-git-send-email-eranian@google.com>

On Thu, Jan 10, 2019 at 05:17:16PM -0800, Stephane Eranian wrote:
> The perf_proc_update_handler() handles /proc/sys/kernel/perf_event_max_sample_rate
> syctl variable.  When the PMU IRQ handler timing monitoring is disabled, i.e,
> when /proc/sys/kernel/perf_cpu_time_max_percent is equal to 0 or 100,
> then no modification to sysctl_perf_event_sample_rate is allowed to prevent
> possible hang from wrong values.
> 
> The problem is that the test to prevent modification is made after the
> sysctl variable is modified in perf_proc_update_handler().
> 
> You get an error:
> 
> $ echo 10001 >/proc/sys/kernel/perf_event_max_sample_rate
> echo: write error: invalid argument
> 
> But the value is still modified causing all sorts of inconsistencies:
> 
> $ cat /proc/sys/kernel/perf_event_max_sample_rate
> 10001
> 
> This patch fixes the problem by moving the parsing of the value after
> the test.
> 
> Signed-off-by: Stephane Eranian <eranian@google.com>

Reviewed-by: Jiri Olsa <jolsa@kernel.org>

jirka

> ---
>  kernel/events/core.c | 14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 3cd13a30f732..e5ede6918050 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -436,18 +436,18 @@ int perf_proc_update_handler(struct ctl_table *table, int write,
>  		void __user *buffer, size_t *lenp,
>  		loff_t *ppos)
>  {
> -	int ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> -
> -	if (ret || !write)
> -		return ret;
> -
> +	int ret;
> +	int perf_cpu = sysctl_perf_cpu_time_max_percent;
>  	/*
>  	 * If throttling is disabled don't allow the write:
>  	 */
> -	if (sysctl_perf_cpu_time_max_percent == 100 ||
> -	    sysctl_perf_cpu_time_max_percent == 0)
> +	if (write && (perf_cpu == 100 || perf_cpu == 0))
>  		return -EINVAL;
>  
> +	ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> +	if (ret || !write)
> +		return ret;
> +
>  	max_samples_per_tick = DIV_ROUND_UP(sysctl_perf_event_sample_rate, HZ);
>  	perf_sample_period_ns = NSEC_PER_SEC / sysctl_perf_event_sample_rate;
>  	update_perf_cpu_limits();
> -- 
> 2.7.4
> 

  parent reply	other threads:[~2019-01-18  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  1:17 [PATCH] perf/core: fix perf_proc_update_handler() bug Stephane Eranian
2019-01-17 21:03 ` Stephane Eranian
2019-01-17 22:09   ` Andi Kleen
2019-01-18 14:14   ` Arnaldo Carvalho de Melo
2019-01-18  9:52 ` Jiri Olsa [this message]
2019-01-22 11:35 ` [tip:perf/urgent] perf core: Fix " tip-bot for Stephane Eranian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190118095251.GB28346@krava \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox