From: "Pali Rohár" <pali@kernel.org>
To: Steve French <sfrench@samba.org>,
Paulo Alcantara <pc@manguebit.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] cifs: Fixes for SMB1 non-UNICODE 8-bit mode
Date: Mon, 28 Oct 2024 12:03:35 +0100 [thread overview]
Message-ID: <20241028110340.29911-1-pali@kernel.org> (raw)
SMB1 protocol supports non-UNICODE (8-bit OEM character set) and
UNICODE (UTF-16) modes. Linux SMB1 client implements both of them but
there are few bugs in processing non-UNICODE mode.
This patch series add a new mount option -o nounicode to disable UNICODE
mode and force usage of non-UNICODE (8-bit OEM character set) mode. This
allows to test non-UNICODE code path against modern/recent SMB servers
which implements and prefer UNICODE mode.
And this patch series fixes SMB1 session setup and reading symlinks when
UNICODE mode is not active.
Tested against Windows Server 2022 SMB1 server and older Samba SMB1
server.
Pali Rohár (5):
cifs: Add new mount option -o nounicode to disable SMB1 UNICODE mode
cifs: Fix encoding of SMB1 Session Setup Kerberos Request in
non-UNICODE mode
cifs: Add support for SMB1 Session Setup NTLMSSP Request in
non-UNICODE mode
cifs: Fix parsing reparse point with native symlink in SMB1
non-UNICODE session
cifs: Remove unicode parameter from parse_reparse_point() function
fs/smb/client/cifsfs.c | 4 ++
fs/smb/client/cifsglob.h | 2 +
fs/smb/client/cifsproto.h | 2 +-
fs/smb/client/cifssmb.c | 5 ++-
fs/smb/client/connect.c | 32 +++++++++++++--
fs/smb/client/fs_context.c | 11 ++++++
fs/smb/client/fs_context.h | 2 +
fs/smb/client/reparse.c | 25 ++++++------
fs/smb/client/sess.c | 81 ++++++++++++++++++++++++--------------
fs/smb/client/smb1ops.c | 4 +-
fs/smb/client/smb2file.c | 1 -
fs/smb/client/smb2proto.h | 2 +-
12 files changed, 118 insertions(+), 53 deletions(-)
--
2.20.1
next reply other threads:[~2024-10-28 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 11:03 Pali Rohár [this message]
2024-10-28 11:03 ` [PATCH 1/5] cifs: Add new mount option -o nounicode to disable SMB1 UNICODE mode Pali Rohár
2024-11-15 13:26 ` Björn JACKE
2024-11-15 13:33 ` Pali Rohár
2024-10-28 11:03 ` [PATCH 2/5] cifs: Fix encoding of SMB1 Session Setup Kerberos Request in non-UNICODE mode Pali Rohár
2024-10-28 11:03 ` [PATCH 3/5] cifs: Add support for SMB1 Session Setup NTLMSSP " Pali Rohár
2024-10-28 11:03 ` [PATCH 4/5] cifs: Fix parsing reparse point with native symlink in SMB1 non-UNICODE session Pali Rohár
2024-10-28 11:03 ` [PATCH 5/5] cifs: Remove unicode parameter from parse_reparse_point() function Pali Rohár
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=20241028110340.29911-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.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