From: Namjae Jeon <linkinjeon@kernel.org>
To: linux-cifs@vger.kernel.org
Cc: "Namjae Jeon" <linkinjeon@kernel.org>,
"Tom Talpey" <tom@talpey.com>,
"Ronnie Sahlberg" <ronniesahlberg@gmail.com>,
"Ralph Böhme" <slow@samba.org>,
"Steve French" <smfrench@gmail.com>,
"Hyunchul Lee" <hyc.lee@gmail.com>,
"Sergey Senozhatsky" <senozhatsky@chromium.org>
Subject: [PATCH v3 0/5] ksmbd: a bunch of patches
Date: Sun, 26 Sep 2021 22:55:38 +0900 [thread overview]
Message-ID: <20210926135543.119127-1-linkinjeon@kernel.org> (raw)
Cc: Tom Talpey <tom@talpey.com>
Cc: Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: Ralph Böhme <slow@samba.org>
Cc: Steve French <smfrench@gmail.com>
Cc: Hyunchul Lee <hyc.lee@gmail.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
v2:
- update comments of smb2_get_data_area_len().
- fix wrong buffer size check in fsctl_query_iface_info_ioctl().
- fix 32bit overflow in smb2_set_info.
v3:
- add buffer check for ByteCount of smb negotiate request.
- Moved buffer check of to the top of loop to avoid unneeded behavior when
out_buf_len is smaller than network_interface_info_ioctl_rsp.
- get correct out_buf_len which doesn't exceed max stream protocol length.
- subtract single smb2_lock_element for correct buffer size check in
ksmbd_smb2_check_message().
Namjae Jeon (5):
ksmbd: add the check to vaildate if stream protocol length exceeds
maximum value
ksmbd: add validation in smb2_ioctl
ksmbd: add request buffer validation in smb2_set_info
ksmbd: check strictly data area in ksmbd_smb2_check_message()
ksmbd: add validation in smb2 negotiate
fs/ksmbd/connection.c | 10 +-
fs/ksmbd/smb2misc.c | 98 +++++++-------
fs/ksmbd/smb2pdu.c | 295 ++++++++++++++++++++++++++++++++----------
fs/ksmbd/smb2pdu.h | 9 ++
fs/ksmbd/smb_common.c | 38 ++++--
fs/ksmbd/smb_common.h | 4 +-
fs/ksmbd/vfs.c | 2 +-
fs/ksmbd/vfs.h | 2 +-
8 files changed, 321 insertions(+), 137 deletions(-)
--
2.25.1
next reply other threads:[~2021-09-26 14:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 13:55 Namjae Jeon [this message]
2021-09-26 13:55 ` [PATCH v3 1/5] ksmbd: add the check to vaildate if stream protocol length exceeds maximum value Namjae Jeon
2021-09-26 13:55 ` [PATCH v3 2/5] ksmbd: add validation in smb2_ioctl Namjae Jeon
2021-09-26 13:55 ` [PATCH v3 3/5] ksmbd: add request buffer validation in smb2_set_info Namjae Jeon
2021-09-26 13:55 ` [PATCH v3 4/5] ksmbd: check strictly data area in ksmbd_smb2_check_message() Namjae Jeon
2021-09-26 13:55 ` [PATCH v3 5/5] ksmbd: add validation in smb2 negotiate Namjae Jeon
2021-09-26 14:27 ` [PATCH v3 0/5] ksmbd: a bunch of patches Ralph Boehme
2021-09-26 15:32 ` Namjae Jeon
2021-09-27 15:42 ` Ralph Boehme
2021-09-27 23:57 ` Namjae Jeon
2021-09-28 3:26 ` Ralph Boehme
2021-09-28 13:43 ` Ralph Boehme
2021-09-28 14:23 ` Namjae Jeon
2021-09-28 16:33 ` Ralph Boehme
2021-09-28 17:33 ` Jeremy Allison
2021-09-29 15:28 ` Tom Talpey
2021-09-29 15:42 ` Jeremy Allison
2021-09-29 16:38 ` Ralph Boehme
2021-09-29 16:45 ` Tom Talpey
2021-09-29 17:08 ` Ralph Boehme
2021-09-29 17:11 ` Steve French
2021-09-29 17:18 ` Ralph Boehme
2021-09-30 0:32 ` Namjae Jeon
2021-09-30 0:51 ` Hyunchul Lee
2021-09-30 7:57 ` Ralph Boehme
2021-09-28 23:27 ` Namjae Jeon
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=20210926135543.119127-1-linkinjeon@kernel.org \
--to=linkinjeon@kernel.org \
--cc=hyc.lee@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=slow@samba.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.com \
/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).