From: "Aurélien Aptel" <aaptel@suse.com>
To: "L. A. Walsh" <linux-cifs@tlinx.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Cc: namjae.jeon@samsung.com, linux-cifs@vger.kernel.org
Subject: Re: cifsd: introduce SMB3 kernel server
Date: Tue, 06 Apr 2021 12:14:43 +0200 [thread overview]
Message-ID: <87h7kj4t4c.fsf@suse.com> (raw)
In-Reply-To: <606C1DD6.80606@tlinx.org>
"L. A. Walsh" <linux-cifs@tlinx.org> writes:
> On 2021/03/18 06:12, Dan Carpenter wrote:
>> [ cifsd: introduce SMB3 kernel server"
> Is it to be Linux policy that it will give in-kernel
> support for only for smb3, or is it planned to move the rest of the proto
> into the kernel as well? It sorta seems like earlier parts of the protocol,
> still dominant on home networks, though it seems linux not supporting
> all of linux's smb devices, from smb2.1 and before.
smb1 (aka cifs) is unsecure, out of support and being actively
deprecated for over 10 years. Microsoft is uninstalling the smb1 server
on Windows updates. That's how hard they want to kill it. Samba is
planning to drop smb1 too eventually.
https://aka.ms/stopusingsmb1
https://aka.ms/smb1rs3
> I'm sure those clients would benefit as well, being kernel services
> could allow for a lower latency with potentially faster response
> time from being a kernel service instead of user-mode client?
> Is that also planned? Isn't the base of an smb3 server the same functions
> of an smb2.x server with the new smb3 extensions?
AFAICT Namjae's ksmbd support smb2 and above.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next prev parent reply other threads:[~2021-04-06 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 13:12 [bug report] cifsd: introduce SMB3 kernel server Dan Carpenter
[not found] ` <CAH2r5msOBAho=1W-eY0paj+4P1J+tuw-vFaRGg8oY50dXu6MHQ@mail.gmail.com>
2021-03-19 8:11 ` Dan Carpenter
2021-03-19 13:12 ` Christoph Hellwig
2021-03-19 15:07 ` Steve French
2021-03-19 15:21 ` Christoph Hellwig
2021-03-19 15:27 ` Steve French
2021-04-06 8:37 ` L. A. Walsh
2021-04-06 10:14 ` Aurélien Aptel [this message]
2021-04-06 22:55 ` cifsd: introduce <SMB2n3> " L. A. Walsh
2021-04-06 23:32 ` 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=87h7kj4t4c.fsf@suse.com \
--to=aaptel@suse.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-cifs@tlinx.org \
--cc=linux-cifs@vger.kernel.org \
--cc=namjae.jeon@samsung.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).