From: Sven Schnelle <svens@linux.ibm.com> Date: 2021-11-29 10:16:33
Hi,
Yafang Shao [off-list ref] writes:
quoted hunk
As the sched:sched_switch tracepoint args are derived from the kernel,
we'd better make it same with the kernel. So the macro TASK_COMM_LEN is
converted to type enum, then all the BPF programs can get it through BTF.
The BPF program which wants to use TASK_COMM_LEN should include the header
vmlinux.h. Regarding the test_stacktrace_map and test_tracepoint, as the
type defined in linux/bpf.h are also defined in vmlinux.h, so we don't
need to include linux/bpf.h again.
Signed-off-by: Yafang Shao <redacted>
Acked-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: David Hildenbrand <redacted>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Arnaldo Carvalho de Melo <redacted>
Cc: Andrii Nakryiko <redacted>
Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: David Hildenbrand <redacted>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Kees Cook <redacted>
Cc: Petr Mladek <pmladek@suse.com>
---
include/linux/sched.h | 9 +++++++--
tools/testing/selftests/bpf/progs/test_stacktrace_map.c | 6 +++---
tools/testing/selftests/bpf/progs/test_tracepoint.c | 6 +++---
3 files changed, 13 insertions(+), 8 deletions(-)
This breaks the trigger-field-variable-support.tc from the ftrace test
suite at least on s390:
echo 'hist:keys=next_comm:wakeup_lat=common_timestamp.usecs-$ts0:onmatch(sched.sched_waking).wakeup_latency($wakeup_lat,next_pid,sched.sched_waking.prio,next_comm) if next_comm=="ping"'
linux/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-field-variable-support.tc: line 15: echo: write error: Invalid argument
I added a debugging line into check_synth_field():
[ 44.091037] field->size 16, hist_field->size 16, field->is_signed 1, hist_field->is_signed 0
Note the difference in the signed field.
Regards
Sven
On Mon, Nov 29, 2021 at 6:13 PM Sven Schnelle [off-list ref] wrote:
Hi,
Yafang Shao [off-list ref] writes:
quoted
As the sched:sched_switch tracepoint args are derived from the kernel,
we'd better make it same with the kernel. So the macro TASK_COMM_LEN is
converted to type enum, then all the BPF programs can get it through BTF.
The BPF program which wants to use TASK_COMM_LEN should include the header
vmlinux.h. Regarding the test_stacktrace_map and test_tracepoint, as the
type defined in linux/bpf.h are also defined in vmlinux.h, so we don't
need to include linux/bpf.h again.
Signed-off-by: Yafang Shao <redacted>
Acked-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: David Hildenbrand <redacted>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Arnaldo Carvalho de Melo <redacted>
Cc: Andrii Nakryiko <redacted>
Cc: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: David Hildenbrand <redacted>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Kees Cook <redacted>
Cc: Petr Mladek <pmladek@suse.com>
---
include/linux/sched.h | 9 +++++++--
tools/testing/selftests/bpf/progs/test_stacktrace_map.c | 6 +++---
tools/testing/selftests/bpf/progs/test_tracepoint.c | 6 +++---
3 files changed, 13 insertions(+), 8 deletions(-)
This breaks the trigger-field-variable-support.tc from the ftrace test
suite at least on s390:
echo 'hist:keys=next_comm:wakeup_lat=common_timestamp.usecs-$ts0:onmatch(sched.sched_waking).wakeup_latency($wakeup_lat,next_pid,sched.sched_waking.prio,next_comm) if next_comm=="ping"'
linux/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-field-variable-support.tc: line 15: echo: write error: Invalid argument
I added a debugging line into check_synth_field():
[ 44.091037] field->size 16, hist_field->size 16, field->is_signed 1, hist_field->is_signed 0
Note the difference in the signed field.
Hi Sven,
Thanks for the report and debugging!
Seems we should explicitly define it as signed ?
Could you pls. help verify it?
From: Steven Rostedt <rostedt@goodmis.org> Date: 2021-11-29 17:33:08
On Mon, 29 Nov 2021 11:13:31 +0100
Sven Schnelle [off-list ref] wrote:
This breaks the trigger-field-variable-support.tc from the ftrace test
suite at least on s390:
echo 'hist:keys=next_comm:wakeup_lat=common_timestamp.usecs-$ts0:onmatch(sched.sched_waking).wakeup_latency($wakeup_lat,next_pid,sched.sched_waking.prio,next_comm) if next_comm=="ping"'
linux/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-field-variable-support.tc: line 15: echo: write error: Invalid argument
I added a debugging line into check_synth_field():
[ 44.091037] field->size 16, hist_field->size 16, field->is_signed 1, hist_field->is_signed 0
Note the difference in the signed field.
That should not break on strings.
Does this fix it (if you keep the patch)?
-- Steve
On Tue, Nov 30, 2021 at 1:30 AM Steven Rostedt [off-list ref] wrote:
quoted hunk
On Mon, 29 Nov 2021 11:13:31 +0100
Sven Schnelle [off-list ref] wrote:
quoted
This breaks the trigger-field-variable-support.tc from the ftrace test
suite at least on s390:
echo 'hist:keys=next_comm:wakeup_lat=common_timestamp.usecs-$ts0:onmatch(sched.sched_waking).wakeup_latency($wakeup_lat,next_pid,sched.sched_waking.prio,next_comm) if next_comm=="ping"'
linux/tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-field-variable-support.tc: line 15: echo: write error: Invalid argument
I added a debugging line into check_synth_field():
[ 44.091037] field->size 16, hist_field->size 16, field->is_signed 1, hist_field->is_signed 0
Note the difference in the signed field.
That should not break on strings.
Does this fix it (if you keep the patch)?
-- Steve