From: "Theodore Tso" <tytso@mit.edu>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 0/7] fix up issues from djwong/fuse4fs-fork
Date: Wed, 6 May 2026 00:04:41 +0200 [thread overview]
Message-ID: <20260505220441.GB49070@macsyma.local> (raw)
In-Reply-To: <20260505155821.GI1101423@frogsfrogsfrogs>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Tue, May 05, 2026 at 08:58:21AM -0700, Darrick J. Wong wrote:
> Hrm. A bisect would be the best (but least conference-friendly) option
> to narrow things down.
Well, a bisect was a bit painful because I had to cherry-pick patches
so I could get a successfull build. But I did finally come up with
the guilty commit, and it's.... surprising at least to me:
commit b0bd58062bbf645942ab4f0aced3bb229f462dde
Author: Darrick J. Wong <djwong@kernel.org>
Date: Thu Aug 28 10:30:40 2025 -0700
fuse2fs: cache symlink targets in the kernel
Speed up symlinks by allowing the kernel to cache them.
Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
I don't know why it made a difference, but this attached patch appears
fix the MacOS regression. Could this be a bug in MacFuse[1]? FWIW, I'm
running MacFuse 5.2.0_1 from MacPorts.
[1] https://macfuse.github.io
I could condition the patch so that we only avoid setting
FUSE_CAP_CACHE_SYMLINKS on MacOS? WDYT?
- Ted
[-- Attachment #2: 0001-Revert-fuse2fs-cache-symlink-targets-in-the-kernel.patch --]
[-- Type: text/plain, Size: 1085 bytes --]
From fb3d2fc975d17d97ed76b2ed76022462a3b329f1 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o <tytso@mit.edu>
Date: Tue, 5 May 2026 23:34:53 +0200
Subject: [PATCH] Revert "fuse2fs: cache symlink targets in the kernel"
This reverts commit b0bd58062bbf645942ab4f0aced3bb229f462dde.
This commit is apparently causing fuse2fs on MacOS to fail without "-o
default_permissions". It's not clear why, but it was determined using
a git bisect, and reverting the commit addresses the regression.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
misc/fuse2fs.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/misc/fuse2fs.c b/misc/fuse2fs.c
index c46cfc23..0f9cefa6 100644
--- a/misc/fuse2fs.c
+++ b/misc/fuse2fs.c
@@ -1593,9 +1593,6 @@ static void *op_init(struct fuse_conn_info *conn,
if (ff->acl)
fuse_set_feature_flag(conn, FUSE_CAP_POSIX_ACL);
#endif
-#ifdef FUSE_CAP_CACHE_SYMLINKS
- fuse_set_feature_flag(conn, FUSE_CAP_CACHE_SYMLINKS);
-#endif
#ifdef FUSE_CAP_NO_EXPORT_SUPPORT
fuse_set_feature_flag(conn, FUSE_CAP_NO_EXPORT_SUPPORT);
#endif
--
2.50.1 (Apple Git-155)
next prev parent reply other threads:[~2026-05-05 22:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 23:32 [PATCH 0/7] fix up issues from djwong/fuse4fs-fork Theodore Ts'o
2026-05-04 23:32 ` [PATCH 1/7] libsupport: drop xbitops.h and define fls() if necessary Theodore Ts'o
2026-05-05 0:11 ` Darrick J. Wong
2026-05-04 23:32 ` [PATCH 2/7] configure.ac: fix disable fuse2fs/fuse4fs by default path Theodore Ts'o
2026-05-05 0:13 ` Darrick J. Wong
2026-05-04 23:32 ` [PATCH 3/7] libsupport: don't use bzero in cache.c Theodore Ts'o
2026-05-05 0:15 ` Darrick J. Wong
2026-05-04 23:32 ` [PATCH 4/7] fuse[24]fs: suppress clang warnings which were breaking the github CI Theodore Ts'o
2026-05-05 0:20 ` Darrick J. Wong
2026-05-04 23:32 ` [PATCH 5/7] libsupport: remove the LIST_HEAD macro from list.h Theodore Ts'o
2026-05-05 0:20 ` Darrick J. Wong
2026-05-04 23:33 ` [PATCH 6/7] libsupport: fix gcc -Wall warnings Theodore Ts'o
2026-05-05 0:20 ` Darrick J. Wong
2026-05-04 23:33 ` [PATCH 7/7] fuse2fs: fix uninitialized variable warnings Theodore Ts'o
2026-05-05 0:26 ` Darrick J. Wong
2026-05-05 0:08 ` [PATCH 0/7] fix up issues from djwong/fuse4fs-fork Darrick J. Wong
2026-05-05 7:21 ` Theodore Tso
2026-05-05 15:58 ` Darrick J. Wong
2026-05-05 22:04 ` Theodore Tso [this message]
2026-05-05 22:56 ` Darrick J. Wong
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=20260505220441.GB49070@macsyma.local \
--to=tytso@mit.edu \
--cc=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.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