From: Steven Rostedt <rostedt@goodmis.org>
To: Baolin Liu <liubaolin12138@163.com>
Cc: almaz.alexandrovich@paragon-software.com, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, linux-trace-kernel@vger.kernel.org,
liubaolin12138@gmail.com, Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v3 v3 5/7] ntfs3: add allocation tracepoints
Date: Tue, 11 Aug 2026 16:04:24 -0400 [thread overview]
Message-ID: <20260811160424.09bfd609@gandalf.local.home> (raw)
In-Reply-To: <20260807010354.2277156-6-liubaolin12138@163.com>
On Fri, 7 Aug 2026 09:03:52 +0800
Baolin Liu <liubaolin12138@163.com> wrote:
> @@ -960,6 +966,9 @@ int attr_data_get_block(struct ntfs_inode *ni, CLST vcn, CLST clen, CLST *lcn,
> if (res)
> *res = NULL;
>
> + trace_ntfs3_attr_data_get_block(&ni->vfs_inode, vcn, clen,
> + new != NULL, zero, no_da);
Hmm, why not just pass new in. It looks like this is the only place that
calls this tracepoint, right?
> +TRACE_EVENT(ntfs3_attr_data_get_block,
> + TP_PROTO(struct inode *inode, u64 vcn, u64 clen, bool create,
> + bool zero, bool no_da),
> + TP_ARGS(inode, vcn, clen, create, zero, no_da),
> + TP_STRUCT__entry(
> + __field(u64, vcn)
> + __field(u64, clen)
> + __field(unsigned long, ino)
> + __field(dev_t, dev)
> + __field(bool, create)
> + __field(bool, zero)
> + __field(bool, no_da)
> + ),
> + TP_fast_assign(
> + __entry->vcn = vcn;
> + __entry->clen = clen;
> + __entry->ino = inode->i_ino;
> + __entry->dev = inode->i_sb->s_dev;
> + __entry->create = create;
Then you can have this be:
__entry->create = new != NULL;
and keep that logic out of the code and out of line in the trace event.
-- Steve
> + __entry->zero = zero;
> + __entry->no_da = no_da;
> + ),
> + TP_printk("dev=(%d,%d) ino=%lu vcn=%llu clen=%llu create=%d zero=%d no_da=%d",
> + MAJOR(__entry->dev), MINOR(__entry->dev), __entry->ino,
> + __entry->vcn, __entry->clen, __entry->create,
> + __entry->zero, __entry->no_da)
> +);
> +
> #endif /* _TRACE_NTFS3_H */
>
> #include <trace/define_trace.h>
next prev parent reply other threads:[~2026-08-11 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 1:03 [PATCH v3 v3 0/7] ntfs3: add tracepoints for core filesystem paths Baolin Liu
2026-08-07 1:03 ` [PATCH v3 v3 1/7] ntfs3: add mount and log replay tracepoints Baolin Liu
2026-08-07 1:03 ` [PATCH v3 v3 2/7] ntfs3: add namei tracepoints Baolin Liu
2026-08-07 1:03 ` [PATCH v3 v3 3/7] ntfs3: add create inode tracepoint Baolin Liu
2026-08-07 1:03 ` [PATCH v3 v3 4/7] ntfs3: add directory index tracepoints Baolin Liu
2026-08-07 1:03 ` [PATCH v3 v3 5/7] ntfs3: add allocation tracepoints Baolin Liu
2026-08-11 20:04 ` Steven Rostedt [this message]
2026-08-11 20:21 ` Steven Rostedt
2026-08-07 1:03 ` [PATCH v3 v3 6/7] ntfs3: add iomap tracepoints Baolin Liu
2026-08-07 1:03 ` [PATCH v3 v3 7/7] ntfs3: add file I/O tracepoints Baolin Liu
2026-08-07 1:07 ` [PATCH v3 v3 0/7] ntfs3: add tracepoints for core filesystem paths liubaolin
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=20260811160424.09bfd609@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=liubaolin12138@163.com \
--cc=liubaolin12138@gmail.com \
--cc=liubaolin@kylinos.cn \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ntfs3@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