linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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] SMB3 Fixes
Date: Sat, 27 Jun 2020 15:11:00 -0500	[thread overview]
Message-ID: <CAH2r5mseacQ-UN7HB8U3KWcJFO5yciGMFPBYLw2GwqhWRD43Xg@mail.gmail.com> (raw)

Please pull the following changes since commit
48778464bb7d346b47157d21ffde2af6b2d39110:

  Linux 5.8-rc2 (2020-06-21 15:45:29 -0700)

are available in the Git repository at:

  git://git.samba.org/sfrench/cifs-2.6.git tags/5.8-rc2-smb3-fixes

for you to fetch changes up to bf1028a41eaf0ce39518cbdda34cdb717f16364a:

  cifs: misc: Use array_size() in if-statement controlling expression
(2020-06-23 19:06:27 -0500)

----------------------------------------------------------------
6 cifs/smb3 fixes, 3 for stable.  Fixes xfstests 451, 313 and 316

Regression test results:
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/360
----------------------------------------------------------------
Gustavo A. R. Silva (1):
      cifs: misc: Use array_size() in if-statement controlling expression

Xiyu Yang (1):
      cifs: Fix cached_fid refcnt leak in open_shroot

Zhang Xiaoxu (4):
      cifs: Fix double add page to memcg when cifs_readpages
      cifs/smb3: Fix data inconsistent when zero file range
      cifs/smb3: Fix data inconsistent when punch hole
      cifs: update ctime and mtime during truncate

 fs/cifs/file.c    | 11 +++++++----
 fs/cifs/inode.c   |  9 +++++++++
 fs/cifs/misc.c    | 16 +++++++---------
 fs/cifs/smb2ops.c | 12 ++++++++++++
 4 files changed, 35 insertions(+), 13 deletions(-)


--
Thanks,

Steve

             reply	other threads:[~2020-06-27 20:11 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27 20:11 Steve French [this message]
2020-06-27 22:45 ` [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-28 22:44 [GIT PULL] SMB3 fixes Steve French
2021-05-29  0:51 ` 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-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-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-03 18:03 Steve French
2019-04-04  6:30 ` 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=CAH2r5mseacQ-UN7HB8U3KWcJFO5yciGMFPBYLw2GwqhWRD43Xg@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).