From: "Darrick J. Wong" <djwong@kernel.org>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, debianbugs@woodall.me.uk,
linux-ext4@vger.kernel.org
Subject: [PATCHSET] fuse2fs: more bug fixes
Date: Wed, 11 Jun 2025 09:43:39 -0700 [thread overview]
Message-ID: <174966018041.3972888.391896904012834159.stgit@frogsfrogsfrogs> (raw)
Hi all,
This series fixes more bugs in fuse2fs.
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-fixes
---
Commits in this patchset:
* libext2fs: fix spurious warnings from fallocate
* fuse2fs: fix error bailout in op_create
* fuse2fs: catch positive errnos coming from libext2fs
---
lib/ext2fs/fallocate.c | 5 +++++
misc/fuse2fs.c | 19 ++++++++++++++++---
2 files changed, 21 insertions(+), 3 deletions(-)
next reply other threads:[~2025-06-11 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 16:43 Darrick J. Wong [this message]
2025-06-11 16:43 ` [PATCH 1/3] libext2fs: fix spurious warnings from fallocate Darrick J. Wong
2025-06-11 16:44 ` [PATCH 2/3] fuse2fs: fix error bailout in op_create Darrick J. Wong
2025-06-11 16:44 ` [PATCH 3/3] fuse2fs: catch positive errnos coming from libext2fs Darrick J. Wong
2025-06-12 16:43 ` Theodore Ts'o
2025-06-12 22:15 ` Darrick J. Wong
2025-06-13 2:04 ` Theodore Ts'o
2025-06-12 22:18 ` [PATCH 4/3] libext2fs: fix bounding error in the extent fallocate code Darrick J. Wong
2025-06-13 1:06 ` [PATCHSET] fuse2fs: more bug fixes Theodore Ts'o
2025-06-14 17:35 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2025-07-06 18:30 Darrick J. Wong
2025-07-31 14:47 ` 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=174966018041.3972888.391896904012834159.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=debianbugs@woodall.me.uk \
--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