Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "R. Diez" <rdiez-2006@rd10.de>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
	linux-cifs@vger.kernel.org, Steve French <smfrench@gmail.com>
Subject: Re: SMB 1.0 broken between Kernel versions 6.2 and 6.5
Date: Tue, 6 Feb 2024 08:29:16 +0100	[thread overview]
Message-ID: <c561e42e-0dfa-46b7-999c-947dc52e7778@rd10.de> (raw)
In-Reply-To: <CAN05THS4HuTfCHEpKG8D3mzo7omoz9mZFVuZGVTH_C2gqhKSHQ@mail.gmail.com>


> Probably the easiest/quickest fix is to enforce rsize/wsize MUST be a
> multiple of page-size ?
> Is there any reason to support other sizes?
> In the mount api you could just round these sizes up to the nearest
> page size multiple.

This feels like a quick shot which may land near your foot.

The documentation does not say why you may want to choose a non-default wsize, but I could think of a scenario where the packet size is chosen based on some network packet fragmentation size. If you suddenly increase the sizes, you may trigger a network performance problem.

Besides, the page size is not always fixed. I am assuming we are talking about PAGE_SIZE on the Linux kernel here, but I don't really know anything about this code. Most architectures have 4 KiB page size, but there is the odd one with 8 KiB, and there is a "kernel-64k" variant for ARM with a 64 KiB page size.

Before rounding any sizes up, I suggest finding out where the issue is, and whether it could be fixed respecting the user-chosen sizes.

Regards,
   rdiez


  reply	other threads:[~2024-02-06  7:29 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 [this message]
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
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=c561e42e-0dfa-46b7-999c-947dc52e7778@rd10.de \
    --to=rdiez-2006@rd10.de \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=smfrench@gmail.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