perf/core: Fix the same task check in perf_event_set_output
PATCH 1/1 perf/core: Fix the same task check in perf_event_set_output
From: Kan Liang <[email protected]>
With the --per-thread option, perf record errors out when sampling with a hardware event and a software event as below.
$ perf record -e cycles,dummy --per-thread ls failed to mmap with 22 (Invalid argument)
The same task is sampled with the two events. The IOC_OUTPUT is invoked to share the mmap memory of the task between the events. In the perf_event_set_output(), the event->ctx is used to check whether the two events are attached to the same task. However, a hardware event and a software event are from different task context. The check always fails.
The task struct is stored in the event->hw.target for each per-thread event. It can be used to determine whether two events are attached to the same task.
The patch can also fix another issue reported months ago.
https://lore.kernel.org/all/[email protected]/
The event->ctx is not ready when the perf_event_set_output() is invoked in the perf_event_open(), while the event->hw.target has been assigned at the moment.
The problem should be a long time issue since commit c3f00c70276d ("perf: Separate find_get_context() from event initialization"). The event->hw.target doesn't exist at that time. Here, the patch which introduces the event->hw.target is used by the Fixes tag.
The problem should still exists between the broken patch and the event->hw.target patch. This patch does not intend to fix that case.
--- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/events/core.c +1 -1
@@ -12080,7 +12080,7 @@ perf_event_set_output(struct perf_event *event, struct perf_event *output_event)/* * If its not a per-cpu rb, it must be the same task. */ -if (output_event->cpu ==-1 && output_event->ctx != event->ctx) +if (output_event->cpu ==-1 && output_event->hw.target != event->hw.target) goto out;/*
Signature · 1 line
2.35.1
Adrian Hunter
reviewerQuoted 30 lines · On 11/07/22 21:07, [email protected] wrote:
From: Kan Liang <[email protected]>
With the --per-thread option, perf record errors out when sampling with a hardware event and a software event as below.
$ perf record -e cycles,dummy --per-thread ls failed to mmap with 22 (Invalid argument)The same task is sampled with the two events. The
IOC_OUTPUTis invoked to share the mmap memory of the task between the events. In theperf_event_set_output(), theevent->ctxis used to check whether the two events are attached to the same task. However, a hardware event and a software event are from different task context. The check always fails.The task struct is stored in the
event->hw.targetfor each per-thread event. It can be used to determine whether two events are attached to the same task.The patch can also fix another issue reported months ago.
https://lore.kernel.org/all/[email protected]/
Theevent->ctxis not ready when theperf_event_set_output()is invoked in theperf_event_open(), while theevent->hw.targethas been assigned at the moment.The problem should be a long time issue since commit
c3f00c70276d("perf: Separatefind_get_context()from event initialization"). Theevent->hw.targetdoesn't exist at that time. Here, the patch which introduces theevent->hw.targetis used by the Fixes tag.
Quoted 6 lines
The problem should still exists between the broken patch and the
event->hw.targetpatch. This patch does not intend to fix that case.Fixes 50f16a8bf9d7 ("perf: Remove type specific target pointers")Reviewed-by Zhengjun Xing <[email protected]>Signed-off-by Kan Liang <[email protected]>
Did this slip through the cracks, or is there more complexity to this case than just sharing the rb?
Quoted 17 lines
--- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/events/core.c +1
-1@@ -12080,7 +12080,7 @@ perf_event_set_output(struct perf_event *event, struct perf_event *output_event)/* * If its not a per-cpu rb, it must be the same task. */ -if (output_event->cpu ==-1 && output_event->ctx != event->ctx) +if (output_event->cpu ==-1 && output_event->hw.target != event->hw.target) goto out;/*
Peter Zijlstra
maintainerQuoted 34 lines · Adrian Hunter
Quoted 33 lines · On 11/07/22 21:07, [email protected] wrote:
From: Kan Liang <[email protected]>
With the --per-thread option, perf record errors out when sampling with a hardware event and a software event as below.
$ perf record -e cycles,dummy --per-thread ls failed to mmap with 22 (Invalid argument)The same task is sampled with the two events. The
IOC_OUTPUTis invoked to share the mmap memory of the task between the events. In theperf_event_set_output(), theevent->ctxis used to check whether the two events are attached to the same task. However, a hardware event and a software event are from different task context. The check always fails.The task struct is stored in the
event->hw.targetfor each per-thread event. It can be used to determine whether two events are attached to the same task.The patch can also fix another issue reported months ago.
https://lore.kernel.org/all/[email protected]/
Theevent->ctxis not ready when theperf_event_set_output()is invoked in theperf_event_open(), while theevent->hw.targethas been assigned at the moment.The problem should be a long time issue since commit
c3f00c70276d("perf: Separatefind_get_context()from event initialization"). Theevent->hw.targetdoesn't exist at that time. Here, the patch which introduces theevent->hw.targetis used by the Fixes tag.The problem should still exists between the broken patch and the
event->hw.targetpatch. This patch does not intend to fix that case.
Quoted 6 lines
Quoted 3 lines
Fixes 50f16a8bf9d7 ("perf: Remove type specific target pointers")Reviewed-by Zhengjun Xing <[email protected]>Signed-off-by Kan Liang <[email protected]>Did this slip through the cracks, or is there more complexity to this case than just sharing the rb?
Both; I very much missed it, but looking at it now, I'm not at all sure it is correct prior to the whole context rewrite we did recently.
So after the rewrite every cpu/task only has a single perf_event_context, and your change below is actually an equivalence.
But prior to that a task could have multiple contexts. Now they got co-scheduled most of the times and it will probably work, but I'm not entirely sure.
So how about we change the Fixes tag to something like:
And anybody that wants to back-port this further gets to either do the full audit and/or keep the pieces.
Hmm?
Quoted 18 lines
Quoted 17 lines
--- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/events/core.c +1
-1@@ -12080,7 +12080,7 @@ perf_event_set_output(struct perf_event *event, struct perf_event *output_event)/* * If its not a per-cpu rb, it must be the same task. */ -if (output_event->cpu ==-1 && output_event->ctx != event->ctx) +if (output_event->cpu ==-1 && output_event->hw.target != event->hw.target) goto out;/*
Adrian Hunter
reviewerQuoted 52 lines · Peter Zijlstra
Quoted 34 lines · Adrian Hunter
Quoted 33 lines · On 11/07/22 21:07, [email protected] wrote:
From: Kan Liang <[email protected]>
With the --per-thread option, perf record errors out when sampling with a hardware event and a software event as below.
$ perf record -e cycles,dummy --per-thread ls failed to mmap with 22 (Invalid argument)The same task is sampled with the two events. The
IOC_OUTPUTis invoked to share the mmap memory of the task between the events. In theperf_event_set_output(), theevent->ctxis used to check whether the two events are attached to the same task. However, a hardware event and a software event are from different task context. The check always fails.The task struct is stored in the
event->hw.targetfor each per-thread event. It can be used to determine whether two events are attached to the same task.The patch can also fix another issue reported months ago.
https://lore.kernel.org/all/[email protected]/
Theevent->ctxis not ready when theperf_event_set_output()is invoked in theperf_event_open(), while theevent->hw.targethas been assigned at the moment.The problem should be a long time issue since commit
c3f00c70276d("perf: Separatefind_get_context()from event initialization"). Theevent->hw.targetdoesn't exist at that time. Here, the patch which introduces theevent->hw.targetis used by the Fixes tag.The problem should still exists between the broken patch and the
event->hw.targetpatch. This patch does not intend to fix that case.Quoted 6 lines
Quoted 3 lines
Fixes 50f16a8bf9d7 ("perf: Remove type specific target pointers")Reviewed-by Zhengjun Xing <[email protected]>Signed-off-by Kan Liang <[email protected]>Did this slip through the cracks, or is there more complexity to this case than just sharing the rb?
Both; I very much missed it, but looking at it now, I'm not at all sure it is correct prior to the whole context rewrite we did recently.
So after the rewrite every cpu/task only has a single
perf_event_context, and your change below is actually an equivalence.But prior to that a task could have multiple contexts. Now they got co-scheduled most of the times and it will probably work, but I'm not entirely sure.
Quoted 8 lines
So how about we change the Fixes tag to something like:
Fixes c3f00c70276d ("perf: Separate find_get_context() from event initialization") # >= v6.2And anybody that wants to back-port this further gets to either do the full audit and/or keep the pieces.
Hmm?
Seems reasonable to me. Kan?
Quoted 19 lines
Quoted 19 lines
Quoted 18 lines
--- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/events/core.c +1
-1@@ -12080,7 +12080,7 @@ perf_event_set_output(struct perf_event *event, struct perf_event *output_event)/* * If its not a per-cpu rb, it must be the same task. */ -if (output_event->cpu ==-1 && output_event->ctx != event->ctx) +if (output_event->cpu ==-1 && output_event->hw.target != event->hw.target) goto out;/*
Quoted 43 lines · Adrian Hunter
Quoted 42 lines · Peter Zijlstra
Quoted 40 lines · Adrian Hunter
Quoted 30 lines · On 11/07/22 21:07, [email protected] wrote:
From: Kan Liang <[email protected]>
With the --per-thread option, perf record errors out when sampling with a hardware event and a software event as below.
$ perf record -e cycles,dummy --per-thread ls failed to mmap with 22 (Invalid argument)The same task is sampled with the two events. The
IOC_OUTPUTis invoked to share the mmap memory of the task between the events. In theperf_event_set_output(), theevent->ctxis used to check whether the two events are attached to the same task. However, a hardware event and a software event are from different task context. The check always fails.The task struct is stored in the
event->hw.targetfor each per-thread event. It can be used to determine whether two events are attached to the same task.The patch can also fix another issue reported months ago.
https://lore.kernel.org/all/[email protected]/
Theevent->ctxis not ready when theperf_event_set_output()is invoked in theperf_event_open(), while theevent->hw.targethas been assigned at the moment.The problem should be a long time issue since commit
c3f00c70276d("perf: Separatefind_get_context()from event initialization"). Theevent->hw.targetdoesn't exist at that time. Here, the patch which introduces theevent->hw.targetis used by the Fixes tag.Quoted 6 lines
The problem should still exists between the broken patch and the
event->hw.targetpatch. This patch does not intend to fix that case.Fixes 50f16a8bf9d7 ("perf: Remove type specific target pointers")Reviewed-by Zhengjun Xing <[email protected]>Signed-off-by Kan Liang <[email protected]>Did this slip through the cracks, or is there more complexity to this case than just sharing the rb?
Quoted 6 lines
Quoted 6 lines
Both; I very much missed it, but looking at it now, I'm not at all sure it is correct prior to the whole context rewrite we did recently.
So after the rewrite every cpu/task only has a single
perf_event_context, and your change below is actually an equivalence.
Right, they are equivalent after the rewrite. I cannot reproduce the "failed to mmap with 22 (Invalid argument)" issue with 6.2 and later anymore.
But the issue reported by Nadav* can still be reproduced with the latest 6.3-rc.*
https://lore.kernel.org/all/[email protected]/
Because the event->ctx is still not set when the perf_event_set_output() is invoked
in the perf_event_open(). The rewrite doesn't change with it.
Quoted 8 lines
Quoted 8 lines
But prior to that a task could have multiple contexts. Now they got co-scheduled most of the times and it will probably work, but I'm not entirely sure.
So how about we change the Fixes tag to something like:
Fixes c3f00c70276d ("perf: Separate find_get_context() from event initialization") # >= v6.2
Not sure if we want the # >= v6.2.
For v6.2 and later, the patch can fixes Nadav's issue.
For v6.1 and earlier, the patch fixes both Nadav's issue and the issue described in the description.
I think I can send a V2 patch to make the history clear in the description.
Thanks,
Kan
Quoted 27 lines
Quoted 4 lines
And anybody that wants to back-port this further gets to either do the full audit and/or keep the pieces.
Hmm?
Seems reasonable to me. Kan?
Quoted 19 lines
Quoted 19 lines
Quoted 18 lines
--- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)kernel/events/core.c +1
-1@@ -12080,7 +12080,7 @@ perf_event_set_output(struct perf_event *event, struct perf_event *output_event)/* * If its not a per-cpu rb, it must be the same task. */ -if (output_event->cpu ==-1 && output_event->ctx != event->ctx) +if (output_event->cpu ==-1 && output_event->hw.target != event->hw.target) goto out;/*