From: Steven Rostedt <rostedt@goodmis.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-xfs@vger.kernel.org, Carlos Maiolino <cem@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: Unused event xfs_growfs_check_rtgeom
Date: Mon, 16 Jun 2025 10:50:10 -0400 [thread overview]
Message-ID: <20250616105010.11efd49f@batman.local.home> (raw)
In-Reply-To: <aEu-U-va9q0QRuX0@infradead.org>
On Thu, 12 Jun 2025 22:59:47 -0700
Christoph Hellwig <hch@infradead.org> wrote:
> On Thu, Jun 12, 2025 at 02:46:08PM -0400, Steven Rostedt wrote:
> > On Thu, 12 Jun 2025 10:47:37 -0700
> > "Darrick J. Wong" <djwong@kernel.org> wrote:
> >
> > > On Thu, Jun 12, 2025 at 01:16:51PM -0400, Steven Rostedt wrote:
> > > > I also found events: xfs_metadir_link and xfs_metadir_start_link are
> > > > defined in fs/xfs/libxfs/xfs_metadir.c in a #ifndef __KERNEL__ section.
> > > >
> > > > Are these events ever used? Why are they called in !__KERNEL__ code?
> > >
> > > libxfs is shared with userspace, and xfs_repair uses them to relink old
> > > quota files.
> > >
> >
> > Does this userspace use these trace events? If so, I think the events
> > need to have an:
>
> They have stubs for them.
If user space only has stubs for them, then why do they exist? The call
to this tracepoints are within #ifndef __KERNEL__ so the kernel will
never call them. Or can the user space stubs be replaced by actual content?
Either case, the events in the header file should be hidden from the kernel.
-- Steve
next prev parent reply other threads:[~2025-06-16 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 17:10 Steven Rostedt
2025-06-12 17:16 ` Steven Rostedt
2025-06-12 17:47 ` Darrick J. Wong
2025-06-12 18:46 ` Steven Rostedt
2025-06-13 5:59 ` Christoph Hellwig
2025-06-16 14:50 ` Steven Rostedt [this message]
2025-06-12 17:47 ` Darrick J. Wong
2025-06-12 20:58 ` Steven Rostedt
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=20250616105010.11efd49f@batman.local.home \
--to=rostedt@goodmis.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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
all inboxes | Powered by JetHome®