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 fixes
Date: Tue, 9 Mar 2021 20:49:00 -0600 [thread overview]
Message-ID: <CAH2r5mt9OWkr_sGjYXSEzRghSsOaO9O6sqfHLM2E07Am15ceAA@mail.gmail.com> (raw)
Please pull the following changes since commit
a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.samba.org/sfrench/cifs-2.6.git tags/5.12-rc2-smb3
for you to fetch changes up to 04ad69c342fc4de5bd23be9ef15ea7574fb1a87e:
cifs: do not send close in compound create+close requests
(2021-03-08 21:23:22 -0600)
----------------------------------------------------------------
6 cifs/smb3 fixes, 3 for stable, including some important mulitchannel
crediting fixes, and fix for statfs error handling
Regression test results:
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/524
----------------------------------------------------------------
Aurelien Aptel (2):
cifs: fix credit accounting for extra channel
cifs: ask for more credit on async read/write code paths
Paulo Alcantara (4):
cifs: print MIDs in decimal notation
cifs: change noisy error message to FYI
cifs: return proper error code in statfs(2)
cifs: do not send close in compound create+close requests
fs/cifs/cifs_debug.c | 2 +-
fs/cifs/cifsfs.c | 2 +-
fs/cifs/cifsglob.h | 19 ++++++++++---------
fs/cifs/connect.c | 14 +++++++-------
fs/cifs/sess.c | 1 +
fs/cifs/smb2inode.c | 1 +
fs/cifs/smb2misc.c | 10 +++++-----
fs/cifs/smb2ops.c | 10 +++++-----
fs/cifs/smb2pdu.c | 6 ++----
fs/cifs/smb2proto.h | 3 +--
fs/cifs/transport.c | 4 ++--
11 files changed, 36 insertions(+), 36 deletions(-)
--
Thanks,
Steve
next reply other threads:[~2021-03-10 2:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 2:49 Steve French [this message]
2021-03-10 18:13 ` [GIT PULL] cifs fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2021-07-10 17:22 [GIT PULL] CIFS Fixes Steve French
2021-07-10 19:08 ` pr-tracker-bot
2021-02-12 18:15 [GIT PULL] cifs fixes Steve French
2021-02-12 20:04 ` Linus Torvalds
2021-02-12 20:39 ` Steve French
2021-02-13 0:26 ` Stefan Metzmacher
2021-02-13 1:02 ` Linus Torvalds
2021-02-13 1:08 ` Stefan Metzmacher
2021-02-13 1:28 ` Linus Torvalds
2021-02-19 23:48 ` Stefan Metzmacher
2021-02-12 21:33 ` Steve French
2021-02-13 20:03 ` pr-tracker-bot
2021-02-06 18:28 Steve French
2021-02-06 23:33 ` pr-tracker-bot
2020-05-17 2:45 [GIT PULL] CIFS Fixes Steve French
2020-05-17 4:45 ` pr-tracker-bot
2015-04-03 3:32 Steve French
2015-02-04 17:42 Steve French
2014-12-29 20:55 Steve French
2014-12-09 15:18 Steve French
[not found] ` <CAH2r5muu_0byHxGJeKxmFinRSv4Aiduj=7U5ysyP-3MzK7e+HQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-10 23:40 ` Linus Torvalds
[not found] ` <CA+55aFzSTqAHhQSUjgQ+6wfD+q614SbEhQuBYhfUaQsmAmGrkQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-11 0:00 ` Steve French
2014-08-20 16:54 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=CAH2r5mt9OWkr_sGjYXSEzRghSsOaO9O6sqfHLM2E07Am15ceAA@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).