mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] perf/core: Avoid removing shared pmu_context on unregister
@ 2017-05-12 10:40 Chris Wilson
  2017-05-12 11:42 ` Chris Wilson
  2017-05-12 11:45 ` [PATCH v2] " Chris Wilson
  0 siblings, 2 replies; 8+ messages in thread
From: Chris Wilson @ 2017-05-12 10:40 UTC (permalink / raw)
  To: linux-kernel
  Cc: Chris Wilson, David Carrillo-Cisneros, Peter Zijlstra,
	Ingo Molnar, # v4 . 11+

In commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
the search for another user of the pmu_cpu_context was removed, and so
we unconditionally free it during perf_pmu_unregister. This leads to
random corruption later and a BUG at mm/percpu.c:689.

Fixes: 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Carrillo-Cisneros <davidcc@google.com>
Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: <stable@vger.kernel.org> # v4.11+
---
 kernel/events/core.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/kernel/events/core.c b/kernel/events/core.c
index aaefaa27e1a6..e62b6207925c 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -9005,7 +9005,8 @@ void perf_pmu_unregister(struct pmu *pmu)
 		device_del(pmu->dev);
 		put_device(pmu->dev);
 	}
-	free_pmu_context(pmu);
+	if (!find_pmu_context(pmu->task_ctx_nr))
+		free_pmu_context(pmu);
 }
 EXPORT_SYMBOL_GPL(perf_pmu_unregister);
 
-- 
2.11.0

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 10:40 [PATCH] perf/core: Avoid removing shared pmu_context on unregister Chris Wilson
@ 2017-05-12 11:42 ` Chris Wilson
  2017-05-12 11:45 ` [PATCH v2] " Chris Wilson
  1 sibling, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2017-05-12 11:42 UTC (permalink / raw)
  To: linux-kernel
  Cc: David Carrillo-Cisneros, Peter Zijlstra, Ingo Molnar, # v4 . 11+

On Fri, May 12, 2017 at 11:40:32AM +0100, Chris Wilson wrote:
> In commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
> the search for another user of the pmu_cpu_context was removed, and so
> we unconditionally free it during perf_pmu_unregister. This leads to
> random corruption later and a BUG at mm/percpu.c:689.
> 
> Fixes: 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: David Carrillo-Cisneros <davidcc@google.com>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: <stable@vger.kernel.org> # v4.11+
> ---
>  kernel/events/core.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index aaefaa27e1a6..e62b6207925c 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -9005,7 +9005,8 @@ void perf_pmu_unregister(struct pmu *pmu)
>  		device_del(pmu->dev);
>  		put_device(pmu->dev);
>  	}
> -	free_pmu_context(pmu);
> +	if (!find_pmu_context(pmu->task_ctx_nr))

Bleh, that find should be under some guard, such as the mutex we held
ealier.

> +		free_pmu_context(pmu);
>  }
>  EXPORT_SYMBOL_GPL(perf_pmu_unregister);
>  
> -- 
> 2.11.0
> 

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [PATCH v2] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 10:40 [PATCH] perf/core: Avoid removing shared pmu_context on unregister Chris Wilson
  2017-05-12 11:42 ` Chris Wilson
@ 2017-05-12 11:45 ` Chris Wilson
  2017-05-12 20:40   ` David Carrillo-Cisneros
  2018-09-21 13:26   ` Peter Zijlstra
  1 sibling, 2 replies; 8+ messages in thread
From: Chris Wilson @ 2017-05-12 11:45 UTC (permalink / raw)
  To: linux-kernel
  Cc: Chris Wilson, David Carrillo-Cisneros, Peter Zijlstra,
	Ingo Molnar, # v4 . 11+

In commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
the search for another user of the pmu_cpu_context was removed, and so
we unconditionally free it during perf_pmu_unregister. This leads to
random corruption later and a BUG at mm/percpu.c:689.

v2: Check for shared pmu_contexts under the mutex.

Fixes: 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: David Carrillo-Cisneros <davidcc@google.com>
Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: <stable@vger.kernel.org> # v4.11+
---
 kernel/events/core.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/kernel/events/core.c b/kernel/events/core.c
index aaefaa27e1a6..4f60f66b35ad 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -8983,10 +8983,12 @@ EXPORT_SYMBOL_GPL(perf_pmu_register);
 void perf_pmu_unregister(struct pmu *pmu)
 {
 	int remove_device;
+	int remove_context;
 
 	mutex_lock(&pmus_lock);
 	remove_device = pmu_bus_running;
 	list_del_rcu(&pmu->entry);
+	remove_context = !find_pmu_context(pmu->task_ctx_nr);
 	mutex_unlock(&pmus_lock);
 
 	/*
@@ -9005,7 +9007,8 @@ void perf_pmu_unregister(struct pmu *pmu)
 		device_del(pmu->dev);
 		put_device(pmu->dev);
 	}
-	free_pmu_context(pmu);
+	if (remove_context)
+		free_pmu_context(pmu);
 }
 EXPORT_SYMBOL_GPL(perf_pmu_unregister);
 
-- 
2.11.0

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 11:45 ` [PATCH v2] " Chris Wilson
@ 2017-05-12 20:40   ` David Carrillo-Cisneros
  2017-05-12 20:41     ` David Carrillo-Cisneros
  2017-05-12 20:52     ` Chris Wilson
  2018-09-21 13:26   ` Peter Zijlstra
  1 sibling, 2 replies; 8+ messages in thread
From: David Carrillo-Cisneros @ 2017-05-12 20:40 UTC (permalink / raw)
  To: Chris Wilson; +Cc: linux-kernel, Peter Zijlstra, Ingo Molnar, # v4 . 11+

On Fri, May 12, 2017 at 4:45 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> In commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
> the search for another user of the pmu_cpu_context was removed, and so
> we unconditionally free it during perf_pmu_unregister. This leads to
> random corruption later and a BUG at mm/percpu.c:689.
>
> v2: Check for shared pmu_contexts under the mutex.
>
> Fixes: 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: David Carrillo-Cisneros <davidcc@google.com>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: <stable@vger.kernel.org> # v4.11+
> ---
>  kernel/events/core.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index aaefaa27e1a6..4f60f66b35ad 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -8983,10 +8983,12 @@ EXPORT_SYMBOL_GPL(perf_pmu_register);
>  void perf_pmu_unregister(struct pmu *pmu)
>  {
>         int remove_device;
> +       int remove_context;
>
>         mutex_lock(&pmus_lock);
>         remove_device = pmu_bus_running;
>         list_del_rcu(&pmu->entry);
> +       remove_context = !find_pmu_context(pmu->task_ctx_nr);
>         mutex_unlock(&pmus_lock);
>
>         /*
> @@ -9005,7 +9007,8 @@ void perf_pmu_unregister(struct pmu *pmu)
>                 device_del(pmu->dev);
>                 put_device(pmu->dev);
>         }
> -       free_pmu_context(pmu);
> +       if (remove_context)
> +               free_pmu_context(pmu);
>  }

Shouldn't be cleaner to keep the check in find_pmu_context, just as it
was before commit 1fd7e4169954 ("perf/core: Remove
perf_cpu_context::unique_pmu")?

(Code below untested)

diff --git a/kernel/events/core.c b/kernel/events/core.c
index 6e75a5c9412d..50d90cbf8418 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -8857,7 +8857,8 @@ static struct perf_cpu_context __percpu
*find_pmu_context(int ctxn)
 static void free_pmu_context(struct pmu *pmu)
 {
        mutex_lock(&pmus_lock);
-       free_percpu(pmu->pmu_cpu_context);
+       if (!find_pmu_context(pmu->task_ctx_nr))
+               free_percpu(pmu->pmu_cpu_context);
        mutex_unlock(&pmus_lock);
 }

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 20:40   ` David Carrillo-Cisneros
@ 2017-05-12 20:41     ` David Carrillo-Cisneros
  2017-05-12 20:52     ` Chris Wilson
  1 sibling, 0 replies; 8+ messages in thread
From: David Carrillo-Cisneros @ 2017-05-12 20:41 UTC (permalink / raw)
  To: Chris Wilson; +Cc: linux-kernel, Peter Zijlstra, Ingo Molnar, # v4 . 11+

> Shouldn't be cleaner to keep the check in find_pmu_context, just as it
I meant in free_pmu_context

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 20:40   ` David Carrillo-Cisneros
  2017-05-12 20:41     ` David Carrillo-Cisneros
@ 2017-05-12 20:52     ` Chris Wilson
  2017-05-12 21:26       ` David Carrillo-Cisneros
  1 sibling, 1 reply; 8+ messages in thread
From: Chris Wilson @ 2017-05-12 20:52 UTC (permalink / raw)
  To: David Carrillo-Cisneros
  Cc: linux-kernel, Peter Zijlstra, Ingo Molnar, # v4 . 11+

On Fri, May 12, 2017 at 01:40:37PM -0700, David Carrillo-Cisneros wrote:
> On Fri, May 12, 2017 at 4:45 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > In commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
> > the search for another user of the pmu_cpu_context was removed, and so
> > we unconditionally free it during perf_pmu_unregister. This leads to
> > random corruption later and a BUG at mm/percpu.c:689.
> >
> > v2: Check for shared pmu_contexts under the mutex.
> >
> > Fixes: 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu")
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: David Carrillo-Cisneros <davidcc@google.com>
> > Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: <stable@vger.kernel.org> # v4.11+
> > ---
> >  kernel/events/core.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index aaefaa27e1a6..4f60f66b35ad 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -8983,10 +8983,12 @@ EXPORT_SYMBOL_GPL(perf_pmu_register);
> >  void perf_pmu_unregister(struct pmu *pmu)
> >  {
> >         int remove_device;
> > +       int remove_context;
> >
> >         mutex_lock(&pmus_lock);
> >         remove_device = pmu_bus_running;
> >         list_del_rcu(&pmu->entry);
> > +       remove_context = !find_pmu_context(pmu->task_ctx_nr);
> >         mutex_unlock(&pmus_lock);
> >
> >         /*
> > @@ -9005,7 +9007,8 @@ void perf_pmu_unregister(struct pmu *pmu)
> >                 device_del(pmu->dev);
> >                 put_device(pmu->dev);
> >         }
> > -       free_pmu_context(pmu);
> > +       if (remove_context)
> > +               free_pmu_context(pmu);
> >  }
> 
> Shouldn't be cleaner to keep the check in find_pmu_context, just as it
> was before commit 1fd7e4169954 ("perf/core: Remove
> perf_cpu_context::unique_pmu")?
> 
> (Code below untested)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 6e75a5c9412d..50d90cbf8418 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -8857,7 +8857,8 @@ static struct perf_cpu_context __percpu
> *find_pmu_context(int ctxn)
>  static void free_pmu_context(struct pmu *pmu)
>  {
>         mutex_lock(&pmus_lock);
> -       free_percpu(pmu->pmu_cpu_context);
> +       if (!find_pmu_context(pmu->task_ctx_nr))
> +               free_percpu(pmu->pmu_cpu_context);
>         mutex_unlock(&pmus_lock);

We have the problem that find_pmu_context looks for a matching
task_ctx_nr, but if a second pmu was registered since our list_del and
before our search, we would wrongly conclude that it was using our pmu
context, but it had actually allocated a new one for itself.

We could do a search by pmu_cpu_context instead, but seems overkill
compared to the remove_context approach.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 20:52     ` Chris Wilson
@ 2017-05-12 21:26       ` David Carrillo-Cisneros
  0 siblings, 0 replies; 8+ messages in thread
From: David Carrillo-Cisneros @ 2017-05-12 21:26 UTC (permalink / raw)
  To: Chris Wilson; +Cc: linux-kernel, Peter Zijlstra, Ingo Molnar, # v4 . 11+

>>
>> Shouldn't be cleaner to keep the check in find_pmu_context, just as it
>> was before commit 1fd7e4169954 ("perf/core: Remove
>> perf_cpu_context::unique_pmu")?
>>
>> (Code below untested)
>>
>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>> index 6e75a5c9412d..50d90cbf8418 100644
>> --- a/kernel/events/core.c
>> +++ b/kernel/events/core.c
>> @@ -8857,7 +8857,8 @@ static struct perf_cpu_context __percpu
>> *find_pmu_context(int ctxn)
>>  static void free_pmu_context(struct pmu *pmu)
>>  {
>>         mutex_lock(&pmus_lock);
>> -       free_percpu(pmu->pmu_cpu_context);
>> +       if (!find_pmu_context(pmu->task_ctx_nr))
>> +               free_percpu(pmu->pmu_cpu_context);
>>         mutex_unlock(&pmus_lock);
>
> We have the problem that find_pmu_context looks for a matching
> task_ctx_nr, but if a second pmu was registered since our list_del and
> before our search, we would wrongly conclude that it was using our pmu
> context, but it had actually allocated a new one for itself.
>

Makes sense. It'd be nice to have that in a comment. Other than that I
am fine with v2.

David

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH v2] perf/core: Avoid removing shared pmu_context on unregister
  2017-05-12 11:45 ` [PATCH v2] " Chris Wilson
  2017-05-12 20:40   ` David Carrillo-Cisneros
@ 2018-09-21 13:26   ` Peter Zijlstra
  1 sibling, 0 replies; 8+ messages in thread
From: Peter Zijlstra @ 2018-09-21 13:26 UTC (permalink / raw)
  To: Chris Wilson
  Cc: linux-kernel, David Carrillo-Cisneros, Ingo Molnar, Mark Rutland,
	Will Deacon

On Fri, May 12, 2017 at 12:45:25PM +0100, Chris Wilson wrote:
> In commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"),
> the search for another user of the pmu_cpu_context was removed, and so
> we unconditionally free it during perf_pmu_unregister. This leads to
> random corruption later and a BUG at mm/percpu.c:689.
> 
> v2: Check for shared pmu_contexts under the mutex.
> 
> Fixes: 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: David Carrillo-Cisneros <davidcc@google.com>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: <stable@vger.kernel.org> # v4.11+
> ---
>  kernel/events/core.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index aaefaa27e1a6..4f60f66b35ad 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -8983,10 +8983,12 @@ EXPORT_SYMBOL_GPL(perf_pmu_register);
>  void perf_pmu_unregister(struct pmu *pmu)
>  {
>  	int remove_device;
> +	int remove_context;
>  
>  	mutex_lock(&pmus_lock);
>  	remove_device = pmu_bus_running;
>  	list_del_rcu(&pmu->entry);
> +	remove_context = !find_pmu_context(pmu->task_ctx_nr);
>  	mutex_unlock(&pmus_lock);
>  
>  	/*
> @@ -9005,7 +9007,8 @@ void perf_pmu_unregister(struct pmu *pmu)
>  		device_del(pmu->dev);
>  		put_device(pmu->dev);
>  	}
> -	free_pmu_context(pmu);
> +	if (remove_context)
> +		free_pmu_context(pmu);
>  }
>  EXPORT_SYMBOL_GPL(perf_pmu_unregister);

I was recently made aware of this patch again; which for some reason
never got resumbitted.

Looking at it I'm not at all sure it is correct.

The first clue is that only task_ctx_nr == perf_sw_context PMUs should
ever be sharing a context; which was noted in the original patch
discussion but that never made it in a comment:

  https://lkml.kernel.org/r/20170118192454.58008-3-davidcc@google.com

And the software PMUs _should_ never get unregistered. Of course it
looks like some:

  arch/powerpc/perf/imc-pmu.c
  drivers/perf/arm_spe_pmu.c

seem to do just that. But I doubt you're running with any of those
drivers active.

Aah, it looks like Will actually fixed this when he did that SPE driver,
see commit:

  df0062b27ebf ("perf/core: Avoid freeing static PMU contexts when PMU is unregistered")

Still, there is another bug there, we should not be doing idr_remove()
outside the lock.

Still, no idea what you hit and why. Or if either or both of these
patches will fix that.

---
diff --git a/kernel/events/core.c b/kernel/events/core.c
index c80549bf82c6..a7ab1d31208c 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -9425,9 +9425,7 @@ static void free_pmu_context(struct pmu *pmu)
 	if (pmu->task_ctx_nr > perf_invalid_context)
 		return;
 
-	mutex_lock(&pmus_lock);
 	free_percpu(pmu->pmu_cpu_context);
-	mutex_unlock(&pmus_lock);
 }
 
 /*
@@ -9697,6 +9695,7 @@ void perf_pmu_unregister(struct pmu *pmu)
 	synchronize_srcu(&pmus_srcu);
 	synchronize_rcu();
 
+	mutex_lock(&pmus_lock);
 	free_percpu(pmu->pmu_disable_count);
 	if (pmu->type >= PERF_TYPE_MAX)
 		idr_remove(&pmu_idr, pmu->type);
@@ -9707,6 +9706,7 @@ void perf_pmu_unregister(struct pmu *pmu)
 		put_device(pmu->dev);
 	}
 	free_pmu_context(pmu);
+	mutex_unlock(&pmus_lock);
 }
 EXPORT_SYMBOL_GPL(perf_pmu_unregister);
 

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2018-09-21 13:27 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-12 10:40 [PATCH] perf/core: Avoid removing shared pmu_context on unregister Chris Wilson
2017-05-12 11:42 ` Chris Wilson
2017-05-12 11:45 ` [PATCH v2] " Chris Wilson
2017-05-12 20:40   ` David Carrillo-Cisneros
2017-05-12 20:41     ` David Carrillo-Cisneros
2017-05-12 20:52     ` Chris Wilson
2017-05-12 21:26       ` David Carrillo-Cisneros
2018-09-21 13:26   ` Peter Zijlstra

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®