From: Paulo Alcantara <pc@cjr.nz>
To: Tom Talpey <tom@talpey.com>, smfrench@gmail.com
Cc: linux-cifs@vger.kernel.org
Subject: Re: [PATCH] cifs: do not query ifaces on smb1 mounts
Date: Tue, 10 Jan 2023 13:45:32 -0300 [thread overview]
Message-ID: <87k01uwd77.fsf@cjr.nz> (raw)
In-Reply-To: <f1e10da3-d2b5-98ed-637b-7773d0fb9b0f@talpey.com>
Tom Talpey <tom@talpey.com> writes:
> On 1/9/2023 11:41 AM, Paulo Alcantara wrote:
>> Users have reported the following error on every 600 seconds
>> (SMB_INTERFACE_POLL_INTERVAL) when mounting SMB1 shares:
>>
>> CIFS: VFS: \\srv\share error -5 on ioctl to get interface list
>>
>> It's supported only by SMB2+, so do not query network interfaces on
>> SMB1 mounts.
>>
>> Fixes: 6e1c1c08cdf3 ("cifs: periodically query network interfaces from server")
>> Signed-off-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
>> ---
>> fs/cifs/cifsglob.h | 1 +
>> fs/cifs/connect.c | 18 ++++++++++++------
>> 2 files changed, 13 insertions(+), 6 deletions(-)
>>
>> diff --git a/fs/cifs/cifsglob.h b/fs/cifs/cifsglob.h
>> index cfdd5bf701a1..931e9d5b21f4 100644
>> --- a/fs/cifs/cifsglob.h
>> +++ b/fs/cifs/cifsglob.h
>> @@ -1240,6 +1240,7 @@ struct cifs_tcon {
>> #ifdef CONFIG_CIFS_DFS_UPCALL
>> struct list_head ulist; /* cache update list */
>> #endif
>> + bool iface_query_poll:1;
>
> Why add such a special-case flag, instead of simply checking the
> dialect, or (betyter) the server's multichannel capability attribute?
>
> It seems fragile and untestable to set a flag like this, especially
> in the tcon, which has nothing to do with supporting the multichannel
> fsctl.
Makes sense. I'll fix it in v2.
Thanks.
next prev parent reply other threads:[~2023-01-10 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 16:41 [PATCH] cifs: do not query ifaces on smb1 mounts Paulo Alcantara
2023-01-10 14:57 ` Tom Talpey
2023-01-10 16:45 ` Paulo Alcantara [this message]
2023-01-10 22:23 ` [PATCH v2] " Paulo Alcantara
2023-01-10 22:31 ` Steve French
2023-01-11 1:42 ` Tom Talpey
2023-01-11 2:24 ` Paulo Alcantara
2023-01-11 2:32 ` Tom Talpey
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=87k01uwd77.fsf@cjr.nz \
--to=pc@cjr.nz \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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