From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Guo Zhengkui <guozhengkui@vivo.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steve French <sfrench@samba.org>,
Hyunchul Lee <hyc.lee@gmail.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@vivo.com
Subject: Re: [PATCH] ksmbd: fix flexible_array.cocci warnings
Date: Thu, 4 Nov 2021 09:10:44 +0900 [thread overview]
Message-ID: <YYMlBCuhyqgdVHiC@google.com> (raw)
In-Reply-To: <CAKYAXd8dd83NoCetj+-Cza5EnTvSZXBbu4UWR0WHT5YjAD-05g@mail.gmail.com>
On (21/11/03 22:51), Namjae Jeon wrote:
>
> 2021-11-03 22:19 GMT+09:00, Guo Zhengkui <guozhengkui@vivo.com>:
> > Fix following coccicheck warning:
> > ./fs/ksmbd/transport_rdma.c:201:20-27: WARNING use flexible-array
> > member instead.
> Is there only one here? It would be better to change them together in
> this patch.
I guess I see more than one
fs/ksmbd/ksmbd_netlink.h: __u8 spnego_blob[0]; /*
fs/ksmbd/ntlmssp.h: __u8 Content[0];
fs/ksmbd/ntlmssp.h: char DomainString[0];
fs/ksmbd/ntlmssp.h: char UserString[0];
fs/ksmbd/smb2pdu.h: __u8 Buffer[0];
fs/ksmbd/smb2pdu.h: __u8 Buffer[0];
fs/ksmbd/smb2pdu.h: char FileName[0]; /* New name to be assigned */
fs/ksmbd/smb2pdu.h: char FileName[0]; /* Name to be assigned to new link */
fs/ksmbd/smb2pdu.h: char FileName[0];
fs/ksmbd/smb2pdu.h: char StreamName[0];
fs/ksmbd/transport_rdma.c: struct scatterlist sg_list[0];
next prev parent reply other threads:[~2021-11-04 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 13:19 [PATCH] ksmbd: fix flexible_array.cocci warnings Guo Zhengkui
2021-11-03 13:51 ` Namjae Jeon
2021-11-04 0:10 ` Sergey Senozhatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-04 4:57 Guo Zhengkui
2021-11-04 12:56 ` kernel test robot
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=YYMlBCuhyqgdVHiC@google.com \
--to=senozhatsky@chromium.org \
--cc=guozhengkui@vivo.com \
--cc=hyc.lee@gmail.com \
--cc=kernel@vivo.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.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