tracefs: Updates for 7.3
cover tracefs: Updates for 7.3
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
tracefs/for-next
Head SHA1: 43a17abc83c6402bffac80a6dd434f8555f457e8
Anubhav Shelat (1):
eventfs: Define event fields before directory creation
Steven Rostedt (1):
eventfs: Add warning for out of bounds pos in __eventfs_iterate()
----
fs/tracefs/event_inode.c | 4 ++++ kernel/trace/trace_events.c | 13 +++++++------ 2 files changed, 11 insertions(+), 6 deletions(-)
PATCH 1/2 eventfs: Define event fields before directory creation
From: Anubhav Shelat <[email protected]>
Move the event_define_fields() call in event_create_dir() before the eventfs directory creation. Previously, a failure after directory creation wouldn't clean up eventfs_inode because the error path didn't call eventfs_remove_dir(). This eliminates the need to clean up the eventfs directories if event_define_fields() fails.
--- kernel/trace/trace_events.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
kernel/trace/trace_events.c +7 -6
@@ -3192,6 +3192,13 @@ event_create_dir(struct eventfs_inode *parent, struct trace_event_file *file)if (WARN_ON_ONCE (strcmp (call->class->system,TRACE_SYSTEM ) ==0 ))return -ENODEV ; + ret =event_define_fields (call); +if (ret <0 ) { +pr_warn ("Could not initialize trace point events/%s\n" , +trace_event_name (call)); +return ret; + } + e_events =event_subsystem_dir (tr, call->class->system, file, parent);if (!e_events)return -ENOMEM ;
@@ -3210,12 +3217,6 @@ event_create_dir(struct eventfs_inode *parent, struct trace_event_file *file) file->ei = ei; - ret =event_define_fields (call); -if (ret <0 ) { -pr_warn ("Could not initialize trace point events/%s\n" , name); -return ret; - } -/* Gets decremented on freeing of the "enable" file */ event_file_get (file);
Signature · 1 line
2.53.0
PATCH 2/2 eventfs: Add warning for out of bounds pos in __eventfs_iterate()
In reply to Steven RostedtFrom: Steven Rostedt <[email protected]>
Sashiko has complained about out of bounds issues if ctx->pos isn't what is expected in __eventfs_iterate()[1]. This would be an issue if the logic that calls __eventfs_iterate() didn't already prevent the code from going out of bounds.
The issue Sashiko brings up is if a user uses lseek64() to put in a position like 0x100000000 which will overflow the integer used to iterate the files. This should never be an issue because both tracefs and eventfs uses the default "maxbytes" for its superblock "s_maxbytes" field which is defined as:
fs/super.c: s->s_maxbytes = MAX_NON_LFS; include/linux/fs.h:#define MAX_NON_LFS ((1UL<<31) - 1)
Where MAX_NON_LFS turns into 0x7fffffff.
Testing this with code to try to pass 0x100000000 to lseek64() to a eventfs directory returns -EINVAL.
But relying on logic for the integrity of a function is not very robust. Add a WARN_ON_ONCE() in case the ctx->pos is out of the expected range.
[1] https://sashiko.dev/#/patchset/20260810160708.3460a2fd%40gandalf.local.home
--- fs/tracefs/event_inode.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/tracefs/event_inode.c +4 -0
@@ -584,6 +584,10 @@ static int eventfs_iterate(struct file *file, struct dir_context *ctx)if (!(ti->flags &TRACEFS_EVENT_INODE ))return -EINVAL ; +/* Logic should prevent ctx->pos from going out of range */ +if (WARN_ON_ONCE (ctx->pos <2 || ctx->pos >0x7fffffffULL )) +return -EINVAL ; + c = ctx->pos -2 ;guard (srcu)(&eventfs_srcu);
Signature · 1 line
2.53.0