From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Baolin Liu <liubaolin12138@163.com>, <rostedt@goodmis.org>,
<mhiramat@kernel.org>, <mathieu.desnoyers@efficios.com>
Cc: <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 v4 0/7] ntfs3: add tracepoints for core filesystem paths
Date: Fri, 16 Oct 2026 16:47:23 +0200 [thread overview]
Message-ID: <b271b809-b310-40f5-aaca-c4f43927cd68@paragon-software.com> (raw)
In-Reply-To: <20260820090504.950475-1-liubaolin12138@163.com>
On 8/20/26 11:04, Baolin Liu wrote:
> From: Baolin Liu <liubaolin@kylinos.cn>
>
> This series adds an initial set of tracepoints for ntfs3 core paths.
>
> The tracepoints cover:
> - mount and log replay
> - namei operations
> - directory index operations
> - allocation and block mapping
> - iomap operations
> - file I/O entry points
>
> Changes in v4 (both addressing review comments on patch 5):
> - ntfs3_attr_data_get_block: pass the "new" pointer to the trace
> event directly and move the "new != NULL" check into
> TP_fast_assign(), keeping that logic out of the call site and only
> executed when the event is enabled
> - ntfs3_attr_set_size_ex: stop sampling the old size with
> i_size_read() in TP_fast_assign() - on the truncate path
> truncate_setsize() has already updated i_size to the new value, so
> the recorded old_size always equaled new_size. Read the actual old
> size from the on-disk attribute record and pass it as an explicit
> parameter; move the call site after the attribute lookup so both
> resident and non-resident attributes are covered
>
> Baolin Liu (7):
> ntfs3: add mount and log replay tracepoints
> ntfs3: add namei tracepoints
> ntfs3: add create inode tracepoint
> ntfs3: add directory index tracepoints
> ntfs3: add allocation tracepoints
> ntfs3: add iomap tracepoints
> ntfs3: add file I/O tracepoints
>
> MAINTAINERS | 1 +
> fs/ntfs3/attrib.c | 12 ++
> fs/ntfs3/dir.c | 3 +
> fs/ntfs3/file.c | 5 +
> fs/ntfs3/fslog.c | 3 +
> fs/ntfs3/index.c | 8 +
> fs/ntfs3/inode.c | 7 +
> fs/ntfs3/namei.c | 5 +
> fs/ntfs3/super.c | 11 +-
> include/trace/events/ntfs3.h | 389 +++++++++++++++++++++++++++++++++++
> 10 files changed, 443 insertions(+), 1 deletion(-)
> create mode 100644 include/trace/events/ntfs3.h
Hello,
Your patches were applied, thank you.
Regards,
Konstantin
prev parent reply other threads:[~2026-10-16 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 9:04 [PATCH v4 0/7] ntfs3: add tracepoints for core filesystem paths Baolin Liu
2026-08-20 9:04 ` [PATCH v4 1/7] ntfs3: add mount and log replay tracepoints Baolin Liu
2026-08-20 9:04 ` [PATCH v4 2/7] ntfs3: add namei tracepoints Baolin Liu
2026-08-20 9:05 ` [PATCH v4 3/7] ntfs3: add create inode tracepoint Baolin Liu
2026-08-20 9:05 ` [PATCH v4 4/7] ntfs3: add directory index tracepoints Baolin Liu
2026-08-20 9:17 ` sashiko-bot
2026-08-20 9:05 ` [PATCH v4 5/7] ntfs3: add allocation tracepoints Baolin Liu
2026-08-20 9:05 ` [PATCH v4 6/7] ntfs3: add iomap tracepoints Baolin Liu
2026-08-20 9:19 ` sashiko-bot
2026-08-20 9:05 ` [PATCH v4 7/7] ntfs3: add file I/O tracepoints Baolin Liu
2026-08-20 9:19 ` sashiko-bot
2026-10-16 14:47 ` Konstantin Komarov [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=b271b809-b310-40f5-aaca-c4f43927cd68@paragon-software.com \
--to=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 \
--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