summaryrefslogtreecommitdiff
path: root/rust/kernel/alloc/allocator
diff options
context:
space:
mode:
authorSteven Rostedt <rostedt@goodmis.org>2026-11-18 12:25:20 -0500
committerSteven Rostedt <rostedt@goodmis.org>2026-11-20 10:02:38 -0500
commit761a77e09577bc7e5fdaff1d11bbff3486a87bf9 (patch)
tree213009feecd06d505f8d1320520364c03bf3262b /rust/kernel/alloc/allocator
parent2891516d90b4dc9d41aa55fde08882e40c7c0336 (diff)
tracing: Do not allow user events to add a system name
User events currently do not support the addition of a system name, but the parsing does not check to see if one is specified. A kprobe can add its own system name with the following command: ~# echo 'p:mysystem/kprobe_event schedule a=%ax' >> dynamic_events ~# ls events/mysystem enable filter kprobe_event But if one tries to do the same with user events: ~# echo 'u:user_events/test u32 a' >> dynamic_events ~# ls events/user_events ls: reading directory 'events/user_events/': Invalid argument enable filter It corrupts the file system as the event added had a '/' in the name. Until user events support specifying system names, just return -EINVAL to prevent the corrupted file system from happening: ~# echo 'u:user_events/test u32 a' >> dynamic_events -bash: echo: write error: Invalid argument Cc: stable@vger.kernel.org Link: https://patch.msgid.link/20261118122520.4a689710@gandalf.local.home Acked-by: Beau Belgrave <beaub@linux.microsoft.com> Fixes: 7f5a08c79df35 ("user_events: Add minimal support for trace_event into ftrace") Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'rust/kernel/alloc/allocator')
0 files changed, 0 insertions, 0 deletions