From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Christoph Hellwig'" <hch@infradead.org>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cifs@vger.kernel.org>, <smfrench@gmail.com>,
<stfrench@microsoft.com>, <willy@infradead.org>,
<aurelien.aptel@gmail.com>,
<linux-cifsd-devel@lists.sourceforge.net>,
<senozhatsky@chromium.org>, <sandeen@sandeen.net>,
<aaptel@suse.com>, <viro@zeniv.linux.org.uk>,
<ronniesahlberg@gmail.com>, <hch@lst.de>,
<dan.carpenter@oracle.com>
Subject: RE: [PATCH v4 02/10] cifsd: add server handler
Date: Wed, 16 Jun 2021 15:49:09 +0900 [thread overview]
Message-ID: <009d01d7627b$b59aa7b0$20cff710$@samsung.com> (raw)
In-Reply-To: <YMhgXsAez9jmeUkW@infradead.org>
Hi Christoph,
> On Wed, Jun 02, 2021 at 12:48:39PM +0900, Namjae Jeon wrote:
> > +/* @FIXME clean up this code */
>
> Hmm, should that be in a submitted codebase?
No, Need to remove it:)
>
> > +#define DATA_STREAM 1
> > +#define DIR_STREAM 2
>
> Should this use a named enum to document the usage a bit better?
Yes, I will do that.
>
> > +#ifndef ksmbd_pr_fmt
> > +#ifdef SUBMOD_NAME
> > +#define ksmbd_pr_fmt(fmt) "ksmbd: " SUBMOD_NAME ": " fmt
> > +#else
> > +#define ksmbd_pr_fmt(fmt) "ksmbd: " fmt
> > +#endif
> > +#endif
>
> Why not use the pr_fmt built into pr_*? With that all the message wrappers except for the _dbg one
> can go away.
Right. Will fix it.
>
> Also can you please decided if this is kcifsd or ksmbd? Using both names is rather confusing.
Ah, Are you saying patch subject prefix and document ? there is no use of kcifsd in source code.
If yes, I will replace it with ksmbd in there.
>
> > +#ifndef ____ksmbd_align
> > +#define ____ksmbd_align __aligned(4)
> > +#endif
>
> No need for the ifndef and all the _ prefixes. More importantly from a quick look it seems like none
> of the structures really needs the attribute anyway.
Okay.
>
> > +#define KSMBD_SHARE_CONFIG_PATH(s) \
> > + ({ \
> > + char *p = (s)->____payload; \
> > + if ((s)->veto_list_sz) \
> > + p += (s)->veto_list_sz + 1; \
> > + p; \
> > + })
>
> Why no inline function?
Okay, will change it to inline function.
>
> > +/* @FIXME */
> > +#include "ksmbd_server.h"
>
> ???
Will remove it.
Thanks for your review!
next prev parent reply other threads:[~2021-06-16 6:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210602035813epcas1p49ba4ff37fe4b784aa76dce67e4036227@epcas1p4.samsung.com>
2021-06-02 3:48 ` [PATCH v4 00/10] cifsd: introduce new SMB3 kernel server Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 01/10] cifsd: add document Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 02/10] cifsd: add server handler Namjae Jeon
2021-06-15 8:10 ` Christoph Hellwig
2021-06-16 6:49 ` Namjae Jeon [this message]
2021-06-02 3:48 ` [PATCH v4 03/10] cifsd: add trasport layers Namjae Jeon
2021-06-15 8:11 ` Christoph Hellwig
2021-06-16 6:49 ` Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 04/10] cifsd: add authentication Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 05/10] cifsd: add smb3 engine part 1 Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 06/10] cifsd: add smb3 engine part 2 Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 07/10] cifsd: add oplock/lease cache mechanism Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 08/10] cifsd: add file operations Namjae Jeon
2021-06-15 8:47 ` Christoph Hellwig
2021-06-16 6:48 ` Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 09/10] cifsd: add Kconfig and Makefile Namjae Jeon
2021-06-02 3:48 ` [PATCH v4 10/10] MAINTAINERS: add cifsd kernel server 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='009d01d7627b$b59aa7b0$20cff710$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=aaptel@suse.com \
--cc=aurelien.aptel@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-cifsd-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=sandeen@sandeen.net \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=stfrench@microsoft.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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