From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Paulo Alcantara <pc@manguebit.com>,
Steve French <stfrench@microsoft.com>,
Sasha Levin <sashal@kernel.org>,
sfrench@samba.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org
Subject: [PATCH AUTOSEL 6.13 18/21] smb: client: fix noisy when tree connecting to DFS interlink targets
Date: Mon, 10 Feb 2025 20:29:51 -0500 [thread overview]
Message-ID: <20250211012954.4096433-18-sashal@kernel.org> (raw)
In-Reply-To: <20250211012954.4096433-1-sashal@kernel.org>
From: Paulo Alcantara <pc@manguebit.com>
[ Upstream commit 773dc23ff81838b6f74d7fabba5a441cc6a93982 ]
When the client attempts to tree connect to a domain-based DFS
namespace from a DFS interlink target, the server will return
STATUS_BAD_NETWORK_NAME and the following will appear on dmesg:
CIFS: VFS: BAD_NETWORK_NAME: \\dom\dfs
Since a DFS share might contain several DFS interlinks and they expire
after 10 minutes, the above message might end up being flooded on
dmesg when mounting or accessing them.
Print this only once per share.
Signed-off-by: Paulo Alcantara (Red Hat) <pc@manguebit.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
fs/smb/client/smb2pdu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/smb/client/smb2pdu.c b/fs/smb/client/smb2pdu.c
index 0577556f0a411..87bc8164c966c 100644
--- a/fs/smb/client/smb2pdu.c
+++ b/fs/smb/client/smb2pdu.c
@@ -2169,7 +2169,7 @@ SMB2_tcon(const unsigned int xid, struct cifs_ses *ses, const char *tree,
tcon_error_exit:
if (rsp && rsp->hdr.Status == STATUS_BAD_NETWORK_NAME)
- cifs_tcon_dbg(VFS, "BAD_NETWORK_NAME: %s\n", tree);
+ cifs_dbg(VFS | ONCE, "BAD_NETWORK_NAME: %s\n", tree);
goto tcon_exit;
}
--
2.39.5
next prev parent reply other threads:[~2025-02-11 1:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 1:29 [PATCH AUTOSEL 6.13 01/21] nvme-fc: go straight to connecting state when initializing Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 02/21] nvme-fc: do not ignore connectivity loss during connecting Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 03/21] hrtimers: Mark is_migration_base() with __always_inline Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 04/21] powercap: call put_device() on an error path in powercap_register_control_type() Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 05/21] btrfs: avoid starting new transaction when cleaning qgroup during subvolume drop Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 06/21] futex: Pass in task to futex_queue() Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 07/21] irqchip/riscv: Ensure ordering of memory writes and IPI writes Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 08/21] iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic() Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 09/21] sched/debug: Provide slice length for fair tasks Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 10/21] platform/x86/intel: pmc: fix ltr decode in pmc_core_ltr_show() Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 11/21] drm/amd/display: Fix out-of-bound accesses Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 12/21] scsi: core: Use GFP_NOIO to avoid circular locking dependency Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 13/21] scsi: ufs: core: Fix error return with query response Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 14/21] scsi: qla1280: Fix kernel oops when debug level > 2 Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 15/21] Revert "drm/amd/display: Use HW lock mgr for PSR1" Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 16/21] kbuild: keep symbols for symbol_get() even with CONFIG_TRIM_UNUSED_KSYMS Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 17/21] ACPI: resource: IRQ override for Eluktronics MECH-17 Sasha Levin
2025-02-11 1:29 ` Sasha Levin [this message]
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 19/21] alpha/elf: Fix misc/setarch test of util-linux by removing 32bit support Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 20/21] vboxsf: fix building with GCC 15 Sasha Levin
2025-02-11 1:29 ` [PATCH AUTOSEL 6.13 21/21] selftests: always check mask returned by statmount(2) Sasha Levin
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=20250211012954.4096433-18-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=stable@vger.kernel.org \
--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