summaryrefslogtreecommitdiff
path: root/include/kunit/attributes.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-01-18 13:22:53 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2025-01-18 13:22:53 -0800
commitfda5e3f284002ea55dac1c98c1498d6dd684046e (patch)
tree2968e6bfd51d1f497dc4ccff8e6b22e5962ef042 /include/kunit/attributes.h
parent595523945be0a5a2f12a1c04772383293fbc04a1 (diff)
parent60295b944ff6805e677c48ae4178532b207d43be (diff)
downloadlwn-master.tar.gz
lwn-master.zip
Merge tag 'trace-v6.13-rc7-2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-traceHEADmaster
Pull tracing fix from Steven Rostedt: "Fix regression in GFP output in trace events It was reported that the GFP flags in trace events went from human readable to just their hex values: gfp_flags=GFP_HIGHUSER_MOVABLE|__GFP_COMP to gfp_flags=0x140cca This was caused by a change that added the use of enums in calculating the GFP flags. As defines get translated into their values in the trace event format files, the user space tooling could easily convert the GFP flags into their symbols via the __print_flags() helper macro. The problem is that enums do not get converted, and the names of the enums show up in the format files and user space tooling cannot translate them. Add TRACE_DEFINE_ENUM() around the enums used for GFP flags which is the tracing infrastructure macro that informs the tracing subsystem what the values for enums and it can then expose that to user space" * tag 'trace-v6.13-rc7-2' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace: tracing: gfp: Fix the GFP enum values shown for user space tracing tools
Diffstat (limited to 'include/kunit/attributes.h')
0 files changed, 0 insertions, 0 deletions