From: "Darrick J. Wong" <djwong@kernel.org>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: [PATCHSET 1/5] fuse2fs: better logging
Date: Thu, 24 Apr 2025 14:38:29 -0700 [thread overview]
Message-ID: <174553064436.1160047.577374015997116030.stgit@frogsfrogsfrogs> (raw)
Hi all,
This series improves logging in fuse2fs by prefixing all messages with
the name of the driver and the device; and ensures that messages are
flusehd immediately.
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-logging
---
Commits in this patchset:
* fuse2fs: enable runtime debugging
* fuse2fs: stop aliasing stderr with ff->err_fp
* fuse2fs: use error logging macro for mount errors
* fuse2fs: make other logging consistent
* fuse2fs: redirect all messages when FUSE2FS_LOGFILE is set
---
misc/fuse2fs.c | 253 ++++++++++++++++++++++++++++++--------------------------
1 file changed, 135 insertions(+), 118 deletions(-)
next reply other threads:[~2025-04-24 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 21:38 Darrick J. Wong [this message]
2025-04-24 21:38 ` [PATCH 1/5] fuse2fs: enable runtime debugging Darrick J. Wong
2025-04-24 21:39 ` [PATCH 2/5] fuse2fs: stop aliasing stderr with ff->err_fp Darrick J. Wong
2025-07-20 8:27 ` Sam James
2025-07-20 18:51 ` Darrick J. Wong
2025-07-21 5:42 ` Darrick J. Wong
2025-07-21 11:41 ` Theodore Ts'o
2025-07-21 17:01 ` Darrick J. Wong
2025-04-24 21:39 ` [PATCH 3/5] fuse2fs: use error logging macro for mount errors Darrick J. Wong
2025-04-24 21:39 ` [PATCH 4/5] fuse2fs: make other logging consistent Darrick J. Wong
2025-04-24 21:40 ` [PATCH 5/5] fuse2fs: redirect all messages when FUSE2FS_LOGFILE is set Darrick J. Wong
2025-05-21 14:51 ` [PATCHSET 1/5] fuse2fs: better logging Theodore Ts'o
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=174553064436.1160047.577374015997116030.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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