From: Sang-Heon Jeon <ekffu200098@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: fuse-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
Luis Henriques <luis@igalia.com>,
Miklos Szeredi <mszeredi@redhat.com>
Subject: [PATCH v2 0/2] fuse: schedule dentry_tree_work only between dentry tree init and cleanup
Date: Sat, 21 Nov 2026 00:00:04 +0900 [thread overview]
Message-ID: <20261120150008.1144420-1-ekffu200098@gmail.com> (raw)
Hello,
inval_wq_set() schedules dentry_tree_work when inval_wq is enabled, but
it can be called before fuse_dentry_tree_init() and after
fuse_dentry_tree_cleanup(). This series makes inval_wq_set() schedule
the work only between the two.
Patch 1 defers scheduling the work until fuse_dentry_tree_init() sets
it up.
Patch 2 does not schedule the work after fuse_dentry_tree_cleanup()
cancels it.
Both patches hold kernel_param_lock(), because a sysfs write can call
inval_wq_set() at the same time.
---
Changes from v1 [1]
- Hold kernel_param_lock() in fuse_dentry_tree_init()
- Add patch 2 to not schedule the work after fuse_dentry_tree_cleanup()
[1] https://lore.kernel.org/all/20261110150250.71520-1-ekffu200098@gmail.com/
---
Sang-Heon Jeon (2):
fuse: defer dentry_tree_work until fuse_dentry_tree_init()
fuse: do not schedule dentry_tree_work after
fuse_dentry_tree_cleanup()
fs/fuse/dir.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
base-commit: ab9787d7e66ac7e6e94fc975b37c5b56fff98ca9
--
2.53.0
next reply other threads:[~2026-11-20 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 15:00 Sang-Heon Jeon [this message]
2026-11-20 15:00 ` [PATCH v2 1/2] fuse: defer dentry_tree_work until fuse_dentry_tree_init() Sang-Heon Jeon
2026-11-20 15:00 ` [PATCH v2 2/2] fuse: do not schedule dentry_tree_work after fuse_dentry_tree_cleanup() Sang-Heon Jeon
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=20261120150008.1144420-1-ekffu200098@gmail.com \
--to=ekffu200098@gmail.com \
--cc=fuse-devel@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
/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
all inboxes | Powered by JetHome®