From: Steve French <smfrench@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: CIFS <linux-cifs@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] cifs/smb3 client fixes
Date: Sat, 6 Nov 2021 08:49:31 -0500 [thread overview]
Message-ID: <CAH2r5mum6Fm=4jybfZ2fcvP9yBioXV4mi6TTjwnTZhasZLnRnQ@mail.gmail.com> (raw)
Please pull the following changes since commit
3906fe9bb7f1a2c8667ae54e967dc8690824f4ea:
Linux 5.15-rc7 (2021-10-25 11:30:31 -0700)
are available in the Git repository at:
git://git.samba.org/sfrench/cifs-2.6.git tags/5.16-rc-part1-smb3-client-fixes
for you to fetch changes up to d7171cd1acf70eb949ece8ccc95be27b3dfcf4da:
smb3: add dynamic trace points for socket connection (2021-11-05
16:20:24 -0500)
----------------------------------------------------------------
7 cifs/smb3 fixes:
- a reconnect fix for stable
- a minor mount option fix
- a debugging improvement for (TCP) connection issues
- refactoring of common code to help ksmbd
Regression test results:
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/826
There is a larger set of fixes (multichannel and DFS related e.g.)
still being tested/reviewed for later in the merge window
----------------------------------------------------------------
Ronnie Sahlberg (4):
cifs: Create a new shared file holding smb2 pdu definitions
cifs: move NEGOTIATE_PROTOCOL definitions out into the common area
cifs: Move more definitions into the shared area
cifs: Move SMB2_Create definitions to the shared area
Shyam Prasad N (1):
cifs: To match file servers, make sure the server hostname matches
Steve French (2):
cifs: add mount parameter tcpnodelay
smb3: add dynamic trace points for socket connection
fs/cifs/cifsfs.c | 1 -
fs/cifs/cifsglob.h | 3 +-
fs/cifs/connect.c | 26 +-
fs/cifs/fs_context.c | 16 ++
fs/cifs/fs_context.h | 2 +
fs/cifs/misc.c | 2 +-
fs/cifs/smb2maperror.c | 16 +-
fs/cifs/smb2misc.c | 47 ++--
fs/cifs/smb2ops.c | 73 +++---
fs/cifs/smb2pdu.c | 187 +++++++-------
fs/cifs/smb2pdu.h | 919
++----------------------------------------------------------------
fs/cifs/smb2proto.h | 2 +-
fs/cifs/smb2transport.c | 36 +--
fs/cifs/trace.h | 71 ++++++
fs/smbfs_common/smb2pdu.h | 989
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
15 files changed, 1299 insertions(+), 1091 deletions(-)
create mode 100644 fs/smbfs_common/smb2pdu.h
--
Thanks,
Steve
next reply other threads:[~2021-11-06 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 13:49 Steve French [this message]
2021-11-06 23:50 ` [GIT PULL] cifs/smb3 client fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-03-26 2:02 Steve French
2023-03-26 16:21 ` pr-tracker-bot
2022-02-04 6:08 Steve French
2022-02-04 17:58 ` pr-tracker-bot
2021-12-10 20:41 Steve French
2021-12-11 1:38 ` pr-tracker-bot
2021-09-24 23:23 Steve French
2021-09-25 19:06 ` pr-tracker-bot
2021-09-18 19:54 Steve French
2021-09-20 23:32 ` pr-tracker-bot
2021-08-30 5:48 Steve French
2021-08-31 16:39 ` Linus Torvalds
2021-08-31 17:08 ` Steve French
2021-08-31 17:43 ` Linus Torvalds
2021-08-31 18:06 ` Steve French
2021-09-14 21:21 ` Steve French
2021-08-31 16:41 ` pr-tracker-bot
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='CAH2r5mum6Fm=4jybfZ2fcvP9yBioXV4mi6TTjwnTZhasZLnRnQ@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.