From 2da03e389866835e29b78a4546c6f1f87aab8fe1 Mon Sep 17 00:00:00 2001 From: Bernd Schubert Date: Sun, 19 Feb 2023 12:52:52 +0100 Subject: Avoid max-idle threads warning If a program with API before 312 did not set max_idle_threads the new default from fuse_parse_cmdline_312() is applied, which sets UINT_MAX (-1). Later in compat fuse_session_loop_mt_32 the old config v1 struct is converted and that conversion prints a warning if the default unset value was used. This could have also happened to programs using the current API, which just apply values struct fuse_cmdline_opts, without checking if the defaults are set. --- lib/fuse_loop_mt.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'lib/fuse_loop_mt.c') diff --git a/lib/fuse_loop_mt.c b/lib/fuse_loop_mt.c index cf9ad86..0200d73 100644 --- a/lib/fuse_loop_mt.c +++ b/lib/fuse_loop_mt.c @@ -464,9 +464,11 @@ void fuse_loop_cfg_set_idle_threads(struct fuse_loop_config *config, unsigned int value) { if (value > FUSE_LOOP_MT_MAX_THREADS) { - fuse_log(FUSE_LOG_ERR, - "Ignoring invalid max threads value " - "%u > max (%u).\n", value, FUSE_LOOP_MT_MAX_THREADS); + if (value != UINT_MAX) + fuse_log(FUSE_LOG_ERR, + "Ignoring invalid max threads value " + "%u > max (%u).\n", value, + FUSE_LOOP_MT_MAX_THREADS); return; } config->max_idle_threads = value; -- cgit v1.2.3