From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Stefan Metzmacher'" <metze@samba.org>
Cc: "'CIFS'" <linux-cifs@vger.kernel.org>,
"'samba-technical'" <samba-technical@lists.samba.org>,
"'Sergey Senozhatsky'" <sergey.senozhatsky@gmail.com>,
"'Hyunchul Lee'" <hyc.lee@gmail.com>,
"'Steve French'" <smfrench@gmail.com>
Subject: RE: updated ksmbd (cifsd)
Date: Tue, 15 Dec 2020 11:28:41 +0900 [thread overview]
Message-ID: <003a01d6d28a$00989dd0$01c9d970$@samsung.com> (raw)
In-Reply-To: <3bf45223-484a-e86a-279a-619a779ceabd@samba.org>
> I just looked briefly, but I'm wondering about a few things:
>
> 1. The xattr's to store additional meta data are not compatible with
> Samba's way of storing things:
> https://git.samba.org/?p=samba.git;a=blob;f=librpc/idl/xattr.idl
>
> In order to make it possible to use the same filesystem with both servers
> it would be great if the well established way used in Samba would be used
> as well.
Yes, Maybe... I will check it after sending ksmbd to linux-next.
> 2. Why does smb2_set_info_sec() have fp->saccess |= FILE_SHARE_DELETE_LE; ?
Because of smb2.acls.GENERIC failure.
TESTING FILE GENERIC BITS
get the original sd
Testing generic bits 0x00000000
time: 2020-12-15 00:00:37.940992
failure: GENERIC [
(../../source4/torture/smb2/acls.c:439) Incorrect status NT_STATUS_SHARING_VIOLATION - should be NT_STATUS_OK
I really don't understand this test. This testcase expect that FILE_DELETE is set in response if desired access
of smb2 open is FILE_MAXIMAL_ACCESS.
I don't know why smb2 open should be allowed although FILE_SHARE_DELETE is not set in previous open in this test.
Can you give me a hint ?
> 3. Why does ksmbd_override_fsids() only reset cred->fs[g|u]id, but group_info
> is kept unchanged, I guess at least the groups array should be set to be empty.
Yes, We need to handle the groups list. Will fix it.
> 4. What is work->saved_cred_level used for in ksmbd_override_fsids()?
> It seems to be unused and adds a lot of complexity.
ksmbd_override_fsids could be called recursively.
work->saved_cred_level prevents ksmbd from overriding fs[g|u]id again.
> 5. Documentation/filesystems/cifsd.rst and fs/cifsd/Kconfig still references https://github.com/cifsd-team/cifsd-tools
> instead of https://github.com/cifsd-team/ksmbd-tools
Okay. Will update it.
> 6. Why is SMB_SERVER_CHECK_CAP_NET_ADMIN an compile time option and why is it off by default?
> I think the behavior should be enforced without a switch.
I can make it default yes. Can you explain more why it should be enforced ?
> These are just some initial thoughts.
Thanks for sharing your review!
>
> metze
next prev parent reply other threads:[~2020-12-15 2:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 1:20 updated ksmbd (cifsd) Steve French
2020-12-14 12:46 ` Namjae Jeon
2020-12-15 2:28 ` Namjae Jeon
2020-12-14 17:45 ` Stefan Metzmacher
2020-12-14 18:48 ` Jeremy Allison
2020-12-15 2:29 ` Namjae Jeon
2020-12-15 4:13 ` Jeremy Allison
2020-12-15 2:28 ` Namjae Jeon [this message]
2020-12-15 14:29 ` Stefan Metzmacher
2020-12-16 3:24 ` Sergey Senozhatsky
2020-12-16 4:21 ` Sergey Senozhatsky
2020-12-17 3:29 ` Sergey Senozhatsky
2020-12-16 8:50 ` 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='003a01d6d28a$00989dd0$01c9d970$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=hyc.lee@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=smfrench@gmail.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