From: liubaolin <liubaolin12138@163.com>
To: Steven Rostedt <rostedt@goodmis.org>
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>,
liubaolin12138@163.com
Subject: Re: [PATCH v1 v1 2/7] ntfs3: add namei tracepoints
Date: Thu, 23 Jul 2026 17:30:33 +0800 [thread overview]
Message-ID: <a36a7376-d750-4f07-a626-e916fe77ff77@163.com> (raw)
In-Reply-To: <20260721170952.26f79352@gandalf.local.home>
Dear Steve,
dentry->d_name.len is the qstr length and does not include the
trailing NUL, so it corresponds to strlen(dentry->d_name.name), rather
than strlen(dentry->d_name.name) + 1.
If you think the extra name_len field here is unnecessary, I can submit
a v2 patch to drop it. Looking forward to your feedback.
Best regards,
Baolin
在 2026/7/22 05:09, Steven Rostedt 写道:
> On Fri, 17 Jul 2026 11:22:43 +0800
> Baolin Liu <liubaolin12138@163.com> wrote:
>
>> +TRACE_EVENT(ntfs3_lookup,
>> + TP_PROTO(struct inode *dir, struct dentry *dentry),
>> + TP_ARGS(dir, dentry),
>> + TP_STRUCT__entry(
>> + __field(dev_t, dev)
>> + __field(unsigned long, parent_ino)
>> + __string(name, dentry->d_name.name)
>> + __field(unsigned int, name_len)
>> + ),
>> + TP_fast_assign(
>> + __entry->dev = dir->i_sb->s_dev;
>> + __entry->parent_ino = dir->i_ino;
>> + __assign_str(name);
>> + __entry->name_len = dentry->d_name.len;
>
> Is dentry->d_name.len not equal to strlen(dentry->d_name.name) + 1 ?
>
> -- Steve
>
>
>> + ),
>> + TP_printk("dev=(%d,%d) parent=%lu name=%s len=%u",
>> + MAJOR(__entry->dev), MINOR(__entry->dev),
>> + __entry->parent_ino, __get_str(name),
>> + __entry->name_len)
>> +);
next prev parent reply other threads:[~2026-07-23 9:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 3:22 [PATCH v1 0/7] ntfs3: add tracepoints for core filesystem paths Baolin Liu
2026-07-17 3:22 ` [PATCH v1 v1 1/7] ntfs3: add mount and log replay tracepoints Baolin Liu
2026-07-17 3:22 ` [PATCH v1 v1 2/7] ntfs3: add namei tracepoints Baolin Liu
2026-07-21 21:09 ` Steven Rostedt
2026-07-23 9:30 ` liubaolin [this message]
2026-07-23 14:17 ` Steven Rostedt
2026-07-17 3:22 ` [PATCH v1 v1 3/7] ntfs3: add create inode tracepoint Baolin Liu
2026-07-17 3:22 ` [PATCH v1 v1 4/7] ntfs3: add directory index tracepoints Baolin Liu
2026-07-17 3:22 ` [PATCH v1 v1 5/7] ntfs3: add allocation tracepoints Baolin Liu
2026-07-17 3:22 ` [PATCH v1 v1 6/7] ntfs3: add iomap tracepoints Baolin Liu
2026-07-17 3:22 ` [PATCH v1 v1 7/7] ntfs3: add file I/O tracepoints Baolin Liu
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=a36a7376-d750-4f07-a626-e916fe77ff77@163.com \
--to=liubaolin12138@163.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=liubaolin12138@gmail.com \
--cc=liubaolin@kylinos.cn \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ntfs3@lists.linux.dev \
--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