From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: fix file_path handling in tracepoints
Date: Thu, 11 Jul 2024 09:01:28 -0700 [thread overview]
Message-ID: <ZpAB2HU8zE41s9j6@infradead.org> (raw)
On Wed, Jul 10, 2024 at 10:43:53PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Since file_path() takes the output buffer as one of its arguments, we
> might as well have it format directly into the tracepoint's char array
> instead of wasting stack space.
This looks sensible to me, but..
The nicest way to format the interesting parts of a file path is to
simply use the magic %pD printk specificer, which removes the entire
need for an extra buffer. It would be kinda nice to use that for
tracing, but I can't see how to accomodate the users of the binary
trace buffer with that. Adding Steven and the trace list for
comments.
> - __array(char, pathname, 256)
> + __array(char, pathname, MAXNAMELEN)
> ),
> TP_fast_assign(
> - char pathname[257];
> char *path;
>
> __entry->ino = file_inode(xf->file)->i_ino;
> + path = file_path(xf->file, __entry->pathname, MAXNAMELEN);
> if (IS_ERR(path))
> + strncpy(__entry->pathname, "(unknown)",
> + sizeof(__entry->pathname));
> ),
> TP_printk("xfino 0x%lx path '%s'",
> __entry->ino,
> diff --git a/fs/xfs/xfs_trace.h b/fs/xfs/xfs_trace.h
> index 56c8333a470bb..0dfb698a43aa4 100644
> --- a/fs/xfs/xfs_trace.h
> +++ b/fs/xfs/xfs_trace.h
> @@ -4715,20 +4715,18 @@ TRACE_EVENT(xmbuf_create,
> TP_STRUCT__entry(
> __field(dev_t, dev)
> __field(unsigned long, ino)
> - __array(char, pathname, 256)
> + __array(char, pathname, MAXNAMELEN)
> ),
> TP_fast_assign(
> - char pathname[257];
> char *path;
> struct file *file = btp->bt_file;
>
> __entry->dev = btp->bt_mount->m_super->s_dev;
> __entry->ino = file_inode(file)->i_ino;
> - memset(pathname, 0, sizeof(pathname));
> - path = file_path(file, pathname, sizeof(pathname) - 1);
> + path = file_path(file, __entry->pathname, MAXNAMELEN);
> if (IS_ERR(path))
> - path = "(unknown)";
> - strncpy(__entry->pathname, path, sizeof(__entry->pathname));
> + strncpy(__entry->pathname, "(unknown)",
> + sizeof(__entry->pathname));
> ),
> TP_printk("dev %d:%d xmino 0x%lx path '%s'",
> MAJOR(__entry->dev), MINOR(__entry->dev),
---end quoted text---
----- End forwarded message -----
next reply other threads:[~2024-07-11 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 16:01 Christoph Hellwig [this message]
2024-07-12 1:17 ` [PATCH] xfs: fix file_path handling in tracepoints Steven Rostedt
2024-07-12 5:03 ` Christoph Hellwig
2024-07-12 12:14 ` 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=ZpAB2HU8zE41s9j6@infradead.org \
--to=hch@infradead.org \
--cc=djwong@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).