linux-kernel - Re: [PATCH 0/5] nfs: more client side tracepoints in write and writeback codepaths

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <0a01b5bb79b9cc012af310f6be72d8b7b32c18fe.camel@kernel.org>
Date: Fri, 29 Aug 2025 10:45:15 -0400
From: Jeff Layton <jlayton@...nel.org>
To: Trond Myklebust <trondmy@...nel.org>, Anna Schumaker <anna@...nel.org>
Cc: linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org, Benjamin
 Coddington <bcodding@...hat.com>
Subject: Re: [PATCH 0/5] nfs: more client side tracepoints in write and
 writeback codepaths

On Fri, 2025-08-08 at 07:40 -0400, Jeff Layton wrote:
> This is a pile of tracepoint additions and cleanups. Most of these I
> plumbed in while tracking down the recent client-side corruption I've
> been hunting. Please consider for v6.18.
> 
> Thanks,
> 
> Signed-off-by: Jeff Layton <jlayton@...nel.org>
> ---
> Jeff Layton (5):
>       nfs: remove trailing space from tracepoint
>       nfs: add tracepoints to nfs_file_read() and nfs_file_write()
>       nfs: new tracepoints around write handling
>       nfs: more in-depth tracing of writepage events
>       nfs: add tracepoints to nfs_writepages()
> 
>  fs/nfs/file.c     |  20 ++++++--
>  fs/nfs/nfstrace.h | 135 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
>  fs/nfs/write.c    |  22 +++++++--
>  3 files changed, 168 insertions(+), 9 deletions(-)
> ---
> base-commit: 0919a5b3b11c699d23bc528df5709f2e3213f6a9
> change-id: 20250807-nfs-tracepoints-f1d84186564d
> 
> Best regards,

Ping? I haven't seen a response, or these in linux-next yet. Can we get
them in soon so they can make v6.18?

They were pretty helpful for tracking down that pgio fix recently.

Thanks,
-- 
Jeff Layton <jlayton@...nel.org>