From: "R. Diez" <rdiez-2006@rd10.de>
To: Steve French <smfrench@gmail.com>
Cc: dhowells@redhat.com, linux-cifs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Matthew Ruffell <matthew.ruffell@canonical.com>
Subject: Re: SMB 1.0 broken between Kernel versions 6.2 and 6.5
Date: Wed, 7 Feb 2024 09:56:00 +0100 [thread overview]
Message-ID: <ec454090-da42-4943-9685-67e2b5a040ca@rd10.de> (raw)
In-Reply-To: <CAH2r5muiod=thF6tnSrgd_LEUCdqy03a2Ln1RU40OMETqt2Z_A@mail.gmail.com>
Hallo Steve:
I wonder what would happen if the SMB server said it can take a maximum of 2048 Bytes, and you insist on 4096. Would the connection still work later on? Wouldn't it be better to abort the connection with a descriptive error message?
You stated that this scenario is very unlikely, but my Linux client is negotiating 16580 bytes at the moment, so if PAGE_SIZE happens to be 64 KiB, that wouldn't be very unlikely any more.
About this other change:
if (round_up(ctx->wsize, 4096) != ctx->wsize)
cifs_dbg(VFS, "wsize should be a multiple of 4096\n")
All my SMB connections have been automated, therefore I am very unlikely to realise of such a warning. It would also mislead people using the current Kernel versions into thinking that this limitation is there to stay.
If the SMB client cannot really honour the user request, wouldn't it be better to fail? In any case, how about mentioning in the error or warning message that this is only a temporary limitation?
The second version of your patch file looks like a VIM swap file. I gather you attached the wrong file. The best way to fix this is obviously to switch to Emacs. ;-)
Regards,
rdiez
next prev parent reply other threads:[~2024-02-07 8:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 22:17 SMB 1.0 broken between Kernel versions 6.2 and 6.5 R. Diez
2024-02-03 22:30 ` Steve French
2024-02-03 23:02 ` R. Diez
2024-02-04 19:15 ` R. Diez
2024-02-05 8:13 ` R. Diez
2024-02-05 9:25 ` David Howells
2024-02-05 9:31 ` David Howells
2024-02-05 9:37 ` R. Diez
2024-02-05 13:12 ` David Howells
2024-02-06 1:30 ` Steve French
2024-02-06 4:05 ` Steve French
2024-02-06 5:51 ` Steve French
2024-02-06 6:20 ` ronnie sahlberg
2024-02-06 7:29 ` R. Diez
2024-02-06 7:16 ` R. Diez
2024-02-06 7:32 ` David Howells
2024-02-06 7:38 ` R. Diez
2024-02-06 8:21 ` David Howells
2024-02-06 15:52 ` Steve French
2024-02-07 3:41 ` Matthew Ruffell
2024-02-07 4:58 ` Steve French
2024-02-07 5:32 ` Steve French
2024-02-07 7:12 ` Steve French
2024-02-07 8:56 ` R. Diez [this message]
2024-02-07 9:58 ` ronnie sahlberg
2024-02-07 14:50 ` Steve French
2024-02-08 9:31 ` Matthew Ruffell
2024-02-09 5:38 ` Steve French
2024-02-09 8:50 ` Matthew Ruffell
2024-02-09 9:41 ` R. Diez
2024-02-09 20:34 ` Steve French
2024-02-09 20:25 ` Steve French
2024-02-15 7:32 ` Steve French
2024-02-16 0:59 ` Shyam Prasad N
2024-02-16 3:46 ` Matthew Ruffell
2024-02-16 4:22 ` Steve French
2024-02-16 5:40 ` Matthew Ruffell
2024-02-08 23:25 ` 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=ec454090-da42-4943-9685-67e2b5a040ca@rd10.de \
--to=rdiez-2006@rd10.de \
--cc=dhowells@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew.ruffell@canonical.com \
--cc=smfrench@gmail.com \
--cc=willy@infradead.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