From: Luis Henriques <luis@igalia.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: mszeredi@redhat.com, fuse-devel@lists.linux.dev,
linux-kernel@vger.kernel.org,
Matt Harvey <mharvey@jumptrading.com>,
kernel-dev@igalia.com, stable@vger.kernel.org
Subject: Re: [PATCH] fuse: fix 'inval_wq' parameter setting during module initialisation
Date: Fri, 6 Nov 2026 10:18:27 +0000 [thread overview]
Message-ID: <au2pczAGgWeloIkw@igalia.com> (raw)
In-Reply-To: <20261019125329.17932-1-luis@igalia.com>
On Mon, Oct 19, 2026 at 01:53:29PM +0100, Luis Henriques wrote:
> If the fuse module is loaded with a 'inval_wq' parameter the inval_wq_set()
> function will schedule work into dentry_tree_work. However this worker is
> not initialised at this point because fuse_dentry_tree_init() will not have
> been executed yet.
>
> This can be fixed by delaying the work scheduling until later if the module
> is still being initialised.
>
> While there, also simplify the sched/cancel by using mod_delayed_work()
> instead of schedule_delayed_work(). This will result in having the period
> being changed immediately instead of waiting for the next reschedule.
>
> Fixes: ab84ad597386 ("fuse: new work queue to periodically invalidate expired dentries")
> Cc: stable@vger.kernel.org
> Signed-off-by: Luis Henriques <luis@igalia.com>
> ---
> Hi!
>
> My initial approach to fix this was to use DECLARE_DELAYED_WORK() to
> initialise the wq statically. But this would then move the problem to
> fuse_dentry_tree_work(), as the worker could still be scheduled before
> the module finishes initialisation.
Ping.
Any comments, or suggestion on a better way to fix this problem?
Cheers,
--
Luis
> fs/fuse/dir.c | 22 ++++++++++++++++------
> 1 file changed, 16 insertions(+), 6 deletions(-)
>
> diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
> index e49b4e874b15..23c8259725c9 100644
> --- a/fs/fuse/dir.c
> +++ b/fs/fuse/dir.c
> @@ -43,7 +43,6 @@ unsigned __read_mostly inval_wq;
> static int inval_wq_set(const char *val, const struct kernel_param *kp)
> {
> unsigned int num;
> - unsigned int old = inval_wq;
> int ret;
>
> if (!val)
> @@ -62,11 +61,14 @@ static int inval_wq_set(const char *val, const struct kernel_param *kp)
>
> *((unsigned int *)kp->arg) = num;
>
> - if (num && !old)
> - schedule_delayed_work(&dentry_tree_work,
> - secs_to_jiffies(num));
> - else if (!num && old)
> - cancel_delayed_work_sync(&dentry_tree_work);
> + /* Only start/stop workqueue if we're past module initialisation */
> + if (!module_is_coming(kp->mod)) {
> + if (num)
> + mod_delayed_work(system_percpu_wq, &dentry_tree_work,
> + secs_to_jiffies(num));
> + else
> + cancel_delayed_work_sync(&dentry_tree_work);
> + }
>
> return 0;
> }
> @@ -224,6 +226,14 @@ void fuse_dentry_tree_init(void)
> dentry_hash[i].tree = RB_ROOT;
> }
> INIT_DELAYED_WORK(&dentry_tree_work, fuse_dentry_tree_work);
> +
> + /*
> + * Start workqueue immediately if the module was loaded with the
> + * 'inval_wq' parameter set
> + */
> + if (inval_wq)
> + schedule_delayed_work(&dentry_tree_work,
> + secs_to_jiffies(inval_wq));
> }
>
> void fuse_dentry_tree_cleanup(void)
next prev parent reply other threads:[~2026-11-06 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 12:53 Luis Henriques
2026-11-06 10:18 ` Luis Henriques [this message]
2026-11-06 11:33 ` Miklos Szeredi
2026-11-06 12:29 ` Luis Henriques
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=au2pczAGgWeloIkw@igalia.com \
--to=luis@igalia.com \
--cc=fuse-devel@lists.linux.dev \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharvey@jumptrading.com \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=stable@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
all inboxes | Powered by JetHome®