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: Namjae Jeon <linkinjeon@kernel.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ksmbd fixes
Date: Fri, 8 Oct 2021 23:59:17 -0500	[thread overview]
Message-ID: <CAH2r5msTLfojvmuejv+hO6CvF8cwuAw9CpiJWxs9a_D7pZfSLw@mail.gmail.com> (raw)

Please pull the following changes since commit
9e1ff307c779ce1f0f810c7ecce3d95bbae40896:

  Linux 5.15-rc4 (2021-10-03 14:08:47 -0700)

are available in the Git repository at:

  git://git.samba.org/ksmbd.git tags/5.15-rc4-ksmbd-fixes

for you to fetch changes up to 64e7875560270b8f669fca9fcd6a689fea56fbeb:

  ksmbd: fix oops from fuse driver (2021-10-07 10:18:36 -0500)

----------------------------------------------------------------
Six fixes for the ksmbd kernel server, including:
- two additional fixes for missing overflow checks
- some cleanup (e.g. remove dead code for less secure dialects that
has been removed, and clarify overflow checks in smb3 decryption)
- update ksmbd internal module version
- fix for an oops

regression test results from current Linux to ksmbd:
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/8/builds/79
----------------------------------------------------------------
Namjae Jeon (6):
      ksmbd: add the check to vaildate if stream protocol length
exceeds maximum value
      ksmbd: check strictly data area in ksmbd_smb2_check_message()
      ksmbd: remove the leftover of smb2.0 dialect support
      ksmbd: use buf_data_size instead of recalculation in smb3_decrypt_req()
      ksmbd: fix version mismatch with out of tree
      ksmbd: fix oops from fuse driver

 fs/ksmbd/connection.c | 10 +++---
 fs/ksmbd/glob.h       |  2 +-
 fs/ksmbd/smb2misc.c   | 98
++++++++++++++++++++++++++++-------------------------------
 fs/ksmbd/smb2ops.c    |  5 ---
 fs/ksmbd/smb2pdu.c    | 59 +++++++++++------------------------
 fs/ksmbd/smb2pdu.h    |  1 -
 fs/ksmbd/smb_common.c | 12 ++------
 fs/ksmbd/smb_common.h |  4 +--
 8 files changed, 77 insertions(+), 114 deletions(-)

-- 
Thanks,

Steve

             reply	other threads:[~2021-10-09  4:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09  4:59 Steve French [this message]
2021-10-09 22:05 ` [GIT PULL] ksmbd fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-12-12  4:44 Steve French
2023-12-12 19:13 ` pr-tracker-bot
2022-01-20  6:14 Steve French
2022-01-20 11:59 ` pr-tracker-bot
2021-12-24  0:45 Steve French
2021-12-24  1:22 ` pr-tracker-bot
2021-11-12 16:19 Steve French
2021-11-13 19:44 ` pr-tracker-bot
2021-10-23 15:06 Steve French
2021-10-24 17:12 ` pr-tracker-bot
2021-09-09 21:59 Steve French
2021-09-09 23:18 ` Steve French
2021-09-09 23:21 ` Linus Torvalds
2021-09-09 23:23 ` 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=CAH2r5msTLfojvmuejv+hO6CvF8cwuAw9CpiJWxs9a_D7pZfSLw@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=linkinjeon@kernel.org \
    --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).