linux-ext4 - [PATCHSET 5/6] fuse2fs: improve operation tracing

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-next>] [day] [month] [year] [list]

Message-ID: <174786678990.1385778.5352134289344525189.stgit@frogsfrogsfrogs>
Date: Wed, 21 May 2025 15:34:59 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: tytso@....edu
Cc: linux-ext4@...r.kernel.org
Subject: [PATCHSET 5/6] fuse2fs: improve operation tracing

Hi all,

This series improves the ability for developers to trace the activities
of fuse2fs by adding more debugging printfs and tracing abilities of
fuse2fs.  It also registers a com_err handler for libext2fs so we can
capture errors coming out of there, and changes filesystem error
reporting to tell us the function name instead of just fuse2fs.c.

If you're going to start using this code, I strongly recommend pulling
from my git trees, which are linked below.

Comments and questions are, as always, welcome.

e2fsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/e2fsprogs.git/log/?h=fuse2fs-tracing
---
Commits in this patchset:
 * fuse2fs: register as an IO flusher thread
 * fuse2fs: hook library error message printing
 * fuse2fs: log all errors being sent to libfuse
 * fuse2fs: print the function name in error messages, not the file name
---
 configure       |   37 +++++++++++++++++++
 configure.ac    |   19 ++++++++++
 lib/config.h.in |    3 ++
 misc/fuse2fs.c  |  109 +++++++++++++++++++++++++++++++++++++++++++++++++++----
 4 files changed, 161 insertions(+), 7 deletions(-)