From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
Steve French <stfrench@microsoft.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the ksmbd tree
Date: Mon, 15 Jul 2024 10:15:51 +1000 [thread overview]
Message-ID: <20240715101551.29fd8268@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi all,
After merging the ksmbd tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/smb/server/vfs_cache.c:39:27: error: 'dh_task' defined but not used [-Werror=unused-variable]
39 | static struct task_struc *dh_task;
| ^~~~~~~
cc1: all warnings being treated as errors
Caused by commit
e70f0abc77e8 ("ksmbd: add durable scavenger timer")
I have applied the following patch for today:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 15 Jul 2024 09:55:23 +1000
Subject: [PATCH] fixup for "ksmbd: add durable scavenger timer"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
fs/smb/server/vfs_cache.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/smb/server/vfs_cache.c b/fs/smb/server/vfs_cache.c
index 2b1a5a3ebf42..4d4ee696e37c 100644
--- a/fs/smb/server/vfs_cache.c
+++ b/fs/smb/server/vfs_cache.c
@@ -36,7 +36,6 @@ static struct kmem_cache *filp_cache;
static bool durable_scavenger_running;
static DEFINE_MUTEX(durable_scavenger_lock);
-static struct task_struc *dh_task;
static wait_queue_head_t dh_wq;
void ksmbd_set_fd_limit(unsigned long limit)
--
2.43.0
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-15 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 0:15 Stephen Rothwell [this message]
2024-07-15 2:48 ` linux-next: build failure after merge of the ksmbd tree Steve French
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=20240715101551.29fd8268@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stfrench@microsoft.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