From: Steve French <smfrench@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Namjae Jeon <namjae.jeon@samsung.com>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [bug report] cifsd: introduce SMB3 kernel server
Date: Fri, 19 Mar 2021 10:07:12 -0500 [thread overview]
Message-ID: <CAH2r5muai5cA7C+Afku-PjgHCm9Zh+SkEiU1jvybL4xi-bre8g@mail.gmail.com> (raw)
In-Reply-To: <20210319131232.GA1057389@infradead.org>
Namjae was working on a better high level summary of status so I would
expect to see a better description of that posted soon. They also
restructured the patch set into a smaller set since rereviewing years
of their incremental patches would be far more time consuming. It has
been presented over the past year or so at various conferences.
Although he had done a good job presenting on cifsd at the big Storage
Developer Conference last year (and also SambaXP etc.), a lot had
improved recently (e.g. it already passes more xfstests than many
servers). There have been posts about cifsd on samba-technical and
linux-cifs where issues overlapped (e.g. compatibility with attributes
that Samba currently saves as xattrs) so the project is well known at
least among the samba community (and apparently it is commonly shipped
in various embedded devices already). There is also a public mailing
list for the project so some of the discussion among the core group of
developers working on it most is probably on that.
I have been focused on testing it with Linux client. See e.g. the run
from a couple days ago
http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/8/builds/26
and I have been pleasantly surprised at the progress, and have been
trying to make sure the test results are very visible, but as Ronnie
and others have mentioned, cifsd has already been very very useful for
testing the client (Samba is harder to tweak for testing).
On Fri, Mar 19, 2021 at 8:14 AM Christoph Hellwig <hch@infradead.org> wrote:
>
> On Thu, Mar 18, 2021 at 04:12:17PM +0300, Dan Carpenter wrote:
> > [ The fs/cifsd/ directory needs to be added to the MAINTAINERS file
> > so this stuff goes through linux-cifs@vger.kernel.org ]
>
> Err, how did this hit linux-next? I've never even seen the code posted
> to a mailing list.
--
Thanks,
Steve
next prev parent reply other threads:[~2021-03-19 15:08 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 [this message]
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
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=CAH2r5muai5cA7C+Afku-PjgHCm9Zh+SkEiU1jvybL4xi-bre8g@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.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).