From: Steve French <smfrench@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, CIFS <linux-cifs@vger.kernel.org>
Subject: [GIT PULL] cifs/smb3 client fixes
Date: Fri, 4 Feb 2022 00:08:12 -0600 [thread overview]
Message-ID: <CAH2r5muqducHGxPtueahyFbqZZkUr1=04JrTuLEzejj_pKjEJQ@mail.gmail.com> (raw)
Please pull the following changes since commit
e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.samba.org/sfrench/cifs-2.6.git tags/5.17-rc3-smb3-client-fixes
for you to fetch changes up to d3b331fb51f326d5b5326010bf2b5841bb86cdc6:
cifs: fix workstation_name for multiuser mounts (2022-02-03 00:16:37 -0600)
----------------------------------------------------------------
SMB3 client fixes including:
- multiple fscache related fixes, reenabling ability to read/write to
cached files for cifs.ko
(that was temporarily disabled for cifs.ko a few weeks ago due to
the recent fscache changes)
- also includes a new fscache helper function ("query_occupancy")
used by above
- fix for multiuser mounts and NTLMSSP auth (workstation name) for stable
- fix locking ordering problem in multichannel code
- trivial malformed comment fix
Unit test results:
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/882
There is an additional DFS reconnection fix, unrelated to this, still
being worked on, that is not included in this P/R
----------------------------------------------------------------
David Howells (5):
Fix a warning about a malformed kernel doc comment in cifs
cifs: Transition from ->readpages() to ->readahead()
netfs, cachefiles: Add a method to query presence of data in the cache
cifs: Implement cache I/O by accessing the cache directly
cifs: Fix the readahead conversion to manage the batch when
reading from cache
Rohith Surabattula (1):
Invalidate fscache cookie only when inode attributes are changed.
Ryan Bair (1):
cifs: fix workstation_name for multiuser mounts
Shyam Prasad N (1):
cifs: unlock chan_lock before calling cifs_put_tcp_session
Documentation/filesystems/netfs_library.rst | 16 ++
fs/cachefiles/io.c | 59 +++++++
fs/cifs/connect.c | 23 ++-
fs/cifs/file.c | 221 ++++++++++-----------------
fs/cifs/fscache.c | 126 ++++++++++++---
fs/cifs/fscache.h | 79 ++++++----
fs/cifs/inode.c | 8 +-
fs/cifs/sess.c | 6 +-
include/linux/netfs.h | 7 +
9 files changed, 346 insertions(+), 199 deletions(-)
--
Thanks,
Steve
next reply other threads:[~2022-02-04 6:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 6:08 Steve French [this message]
2022-02-04 17:58 ` [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
2021-12-10 20:41 Steve French
2021-12-11 1:38 ` pr-tracker-bot
2021-11-06 13:49 Steve French
2021-11-06 23:50 ` 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='CAH2r5muqducHGxPtueahyFbqZZkUr1=04JrTuLEzejj_pKjEJQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).