From: sashiko-bot@kernel.org
To: "Steven Rostedt" <rostedt@goodmis.org>,
"Linux Trace Kernel" <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH v8] tracefs: Add read-only eventfs filesystem at /sys/kernel/events
Date: Tue, 03 Nov 2026 23:14:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-196186@kernel.org> (raw)
In-Reply-To: <20261103175534.6bd94b13@gandalf.local.home>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] tracefs: mismatched kernel-doc function name for __eventfs_root_lookup()
--
commit a184dfa06e9d76ab752cc43b8175907e50ee86f0
Author: Anubhav Shelat <ashelat@redhat.com>
tracefs: Add read-only eventfs filesystem at /sys/kernel/events
This commit introduces a read-only eventfs pseudo-filesystem mounted at
/sys/kernel/events that exposes trace event format and id files to
unprivileged users by reusing the existing eventfs_inode lazy-lookup
infrastructure.
> diff --git a/fs/tracefs/event_inode.c b/fs/tracefs/event_inode.c
> index 6e3513b13cfa2..8875b0241453b 100644
> --- a/fs/tracefs/event_inode.c
> +++ b/fs/tracefs/event_inode.c
[ ... ]
> @@ -521,14 +647,16 @@ lookup_file_dentry(struct dentry *dentry,
> * @dir: in which a lookup is being done
> * @dentry: file/dir dentry
> * @flags: Just passed to simple_lookup()
> + * @ro: Denote if this is from a read-only eventfs
> *
> * Used to create dynamic file/dir with-in @dir, search with-in @ei
> * list, if @dentry found go ahead and create the file/dir
> */
>
> -static struct dentry *eventfs_root_lookup(struct inode *dir,
> - struct dentry *dentry,
> - unsigned int flags)
> +static struct dentry *__eventfs_root_lookup(struct inode *dir,
> + struct dentry *dentry,
> + unsigned int flags,
> + bool ro)
[Severity: Low]
As reported by Sashiko on v5 [1], this isn't a bug, but since
eventfs_root_lookup() in fs/tracefs/event_inode.c was renamed to
__eventfs_root_lookup(), should the function name in the kernel-doc comment
header above it also be updated to __eventfs_root_lookup to avoid a W=1
kernel-doc prototype mismatch warning?
[1] https://lore.kernel.org/r/sashiko-outbox-195864@kernel.org
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103175534.6bd94b13@gandalf.local.home?part=1
prev parent reply other threads:[~2026-11-03 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:55 [PATCH v8] tracefs: Add read-only eventfs filesystem at /sys/kernel/events Steven Rostedt
2026-11-03 23:14 ` sashiko-bot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=sashiko-outbox-196186@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashiko-reviews@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox