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] SMB3 Fixes
Date: Wed, 3 Apr 2019 13:03:47 -0500 [thread overview]
Message-ID: <CAH2r5mv70K=Mj7ehKB2iAZc95emcWGYC5eBKOV-1tkD=euyatQ@mail.gmail.com> (raw)
Please pull the following changes since commit
5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539:
Merge branch 'work.aio' of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2019-04-01
08:28:36 -0700)
are available in the Git repository at:
git://git.samba.org/sfrench/cifs-2.6.git tags/5.1-rc3-smb3-fixes
for you to fetch changes up to 4811e3096daaa56e145a1d2bec45e2e9fe790729:
cifs: a smb2_validate_and_copy_iov failure does not mean the handle
is invalid. (2019-04-01 14:33:38 -0500)
----------------------------------------------------------------
four smb3 fixes for stable
- fix an open path where we had an unitialized structure
- fix for snapshot (previous version) enumeration
- allow reconnect timeout on handles to be configurable to better
handle network or server crash
----------------------------------------------------------------
Ronnie Sahlberg (2):
cifs: fix kref underflow in close_shroot()
cifs: a smb2_validate_and_copy_iov failure does not mean the
handle is invalid.
Steve French (2):
smb3: Fix enumerating snapshots to Azure
SMB3: Allow persistent handle timeout to be configurable on mount
fs/cifs/cifsfs.c | 2 ++
fs/cifs/cifsglob.h | 8 ++++++++
fs/cifs/connect.c | 30 +++++++++++++++++++++++++++++-
fs/cifs/smb2file.c | 6 ++++--
fs/cifs/smb2ops.c | 68
++++++++++++++++++++++++++++++++++++++++++--------------------------
fs/cifs/smb2pdu.c | 49 +++++++++++++++++++++++++++++++++----------------
fs/cifs/smb2proto.h | 5 +++--
7 files changed, 121 insertions(+), 47 deletions(-)
--
Thanks,
Steve
next reply other threads:[~2019-04-03 18:04 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 18:03 Steve French [this message]
2019-04-04 6:30 ` [GIT PULL] SMB3 Fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2024-04-23 4:27 [GIT PULL] smb3 fixes Steve French
2024-04-23 16:44 ` pr-tracker-bot
2022-01-22 5:51 Steve French
2022-01-22 9:40 ` pr-tracker-bot
2021-05-21 16:20 [GIT PULL] SMB3 Fixes Steve French
2021-05-21 23:31 ` pr-tracker-bot
2021-05-09 14:37 Steve French
2021-05-09 20:49 ` pr-tracker-bot
2021-04-09 1:48 Steve French
2021-04-09 2:04 ` pr-tracker-bot
2021-01-24 4:44 Steve French
2021-01-24 18:34 ` pr-tracker-bot
2020-12-05 1:23 Steve French
2020-12-05 19:21 ` pr-tracker-bot
2020-12-01 22:28 Steve French
2020-12-01 23:49 ` pr-tracker-bot
2020-11-24 22:00 Steve French
2020-11-24 23:47 ` pr-tracker-bot
2020-08-15 5:32 [GIT PULL] SMB3 fixes Steve French
2020-08-16 1:55 ` pr-tracker-bot
2020-07-11 0:53 [GIT PULL] SMB3 Fixes Steve French
2020-07-11 4:25 ` pr-tracker-bot
2020-06-27 20:11 Steve French
2020-06-27 22:45 ` pr-tracker-bot
2020-04-19 12:50 Steve French
2020-04-19 19:20 ` pr-tracker-bot
2020-01-28 18:31 Steve French
2020-01-28 23:40 ` pr-tracker-bot
2019-12-29 5:06 Steve French
2019-12-29 19:35 ` pr-tracker-bot
2019-12-08 5:41 Steve French
2019-12-08 21:40 ` pr-tracker-bot
2019-10-11 20:40 [GIT PULL] SMB3 fixes Steve French
2019-10-11 21:35 ` pr-tracker-bot
2019-09-28 21:46 [GIT PULL] SMB3 Fixes Steve French
2019-09-28 21:36 Steve French
2019-09-30 3:05 ` pr-tracker-bot
2019-08-08 6:49 Steve French
2019-08-09 1:30 ` pr-tracker-bot
2019-07-20 23:48 Steve French
2019-07-21 17:35 ` pr-tracker-bot
2019-06-21 2:02 Steve French
2019-06-21 17:25 ` pr-tracker-bot
2019-05-31 17:55 Steve French
2019-05-31 20:55 ` pr-tracker-bot
2019-05-18 3:37 Steve French
2019-05-19 19:15 ` pr-tracker-bot
2019-04-26 0:23 Steve French
2019-04-26 16:50 ` pr-tracker-bot
2019-04-17 19:40 Steve French
2019-04-17 21:15 ` pr-tracker-bot
2019-03-24 3:22 Steve French
2019-03-24 18:40 ` pr-tracker-bot
2019-03-08 16:54 [GIT][PULL] smb3 fixes Steve French
2019-03-09 19:55 ` 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='CAH2r5mv70K=Mj7ehKB2iAZc95emcWGYC5eBKOV-1tkD=euyatQ@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).