From: Steve French <smfrench@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Namjae Jeon <linkinjeon@kernel.org>,
CIFS <linux-cifs@vger.kernel.org>
Subject: [GIT PULL] ksmbd fixes
Date: Mon, 11 Dec 2023 22:44:32 -0600 [thread overview]
Message-ID: <CAH2r5mscEZygkgAK49pr0Tf89eJAhngE35AUo+Rmt1800m9TnQ@mail.gmail.com> (raw)
Please pull the following changes since commit
33cc938e65a98f1d29d0a18403dbbee050dcad9a:
Linux 6.7-rc4 (2023-12-03 18:52:56 +0900)
are available in the Git repository at:
git://git.samba.org/ksmbd.git tags/6.7-rc5-ksmbd-server-fixes
for you to fetch changes up to 13736654481198e519059d4a2e2e3b20fa9fdb3e:
ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE (2023-12-08
10:11:33 -0600)
----------------------------------------------------------------
Nine smb3 server fixes
- Memory leak fix (in lock error path)
- Two fixes for create with allocation size
- FIx for potential UAF in lease break error path
- Five directory lease (caching) fixes found during additional recent testing
----------------------------------------------------------------
Namjae Jeon (8):
ksmbd: set epoch in create context v2 lease
ksmbd: set v2 lease capability
ksmbd: downgrade RWH lease caching state to RH for directory
ksmbd: send v2 lease break notification for directory
ksmbd: lazy v2 lease break on smb2_write()
ksmbd: avoid duplicate opinfo_put() call on error of
smb21_lease_break_ack()
ksmbd: fix wrong allocation size update in smb2_open()
ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE
Zizhi Wo (1):
ksmbd: fix memory leak in smb2_lock()
fs/smb/common/smb2pdu.h | 3 +-
fs/smb/server/oplock.c | 115
+++++++++++++++++++++++++++++++++++++++++++------
fs/smb/server/oplock.h | 8 +++-
fs/smb/server/smb2ops.c | 9 ++--
fs/smb/server/smb2pdu.c | 62 ++++++++++++++------------
fs/smb/server/vfs.c | 3 ++
fs/smb/server/vfs_cache.c | 13 +++++-
fs/smb/server/vfs_cache.h | 3 ++
8 files changed, 171 insertions(+), 45 deletions(-)
--
Thanks,
Steve
next reply other threads:[~2023-12-12 4:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 4:44 Steve French [this message]
2023-12-12 19:13 ` [GIT PULL] ksmbd fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
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-10-09 4:59 Steve French
2021-10-09 22:05 ` 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=CAH2r5mscEZygkgAK49pr0Tf89eJAhngE35AUo+Rmt1800m9TnQ@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).