From: Jaehee Park <jhpark1013@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: replace zero-element array with flexible-array
Date: Wed, 13 Apr 2022 00:50:31 -0400 [thread overview]
Message-ID: <20220413045031.GC3357359@jaehee-ThinkPad-X1-Extreme> (raw)
In-Reply-To: <YlUGp+/BzMSm3oDC@kroah.com>
On Tue, Apr 12, 2022 at 06:57:11AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 12, 2022 at 06:56:12AM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Apr 11, 2022 at 05:14:11PM -0400, Jaehee Park wrote:
> > > Zero-length and one-element arrays are deprecated. Flexible-array
> > > members should be used instead. Flexible-array members are
> > > recommended because this is the way the kernel expects dynamically
> > > sized trailing elements to be declared.
> > > Refer to Documentation/process/deprecated.rst.
> > >
> > > Change the zero-length array, buf, in the struct
> > > gb_usb_hub_control_response to a flexible array. And add wLength as a
> > > member of the struct so that the struct is not a zero-sized struct.
> > >
> > > Issue found by flexible_array coccinelle script.
> > >
> > > Signed-off-by: Jaehee Park <jhpark1013@gmail.com>
> > > ---
> > >
> > > I have a question for the authors:
> > > I saw a fixme comment in the hub_control function in usb.c:
> > > / FIXME: handle unspecified lengths /
> > >
> > > I was wondering why this comment was left there?
> > >
> > > In this patch, I'm using this struct:
> > >
> > > struct gb_usb_hub_control_response {
> > > __le16 wLength;
> > > u8 buf[];
> > > };
> > >
> > > And instead of using response_size, I'm doing this:
> > >
> > > struct gb_usb_hub_control_response *response;
> > > And using sizeof(*response) as the input to gb_operation_create.
> > >
> > > Would the flexible array address the handling of unspecified lengths
> > > issue (in the fixme comment)?
> >
> > No, you can not change the format of the data on the bus without also
> > changing the firmware in the device and usually the specification as
> > well.
> >
> > > drivers/staging/greybus/usb.c | 7 +++----
> > > 1 file changed, 3 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/drivers/staging/greybus/usb.c b/drivers/staging/greybus/usb.c
> > > index 8e9d9d59a357..d0b2422401df 100644
> > > --- a/drivers/staging/greybus/usb.c
> > > +++ b/drivers/staging/greybus/usb.c
> > > @@ -27,7 +27,8 @@ struct gb_usb_hub_control_request {
> > > };
> > >
> > > struct gb_usb_hub_control_response {
> > > - u8 buf[0];
> > > + __le16 wLength;
> > > + u8 buf[];
> >
> > What is wrong with buf[0] here?
> >
> > You can fix this in other ways if you really understand the difference
> > between [0] and [] in C. Please look at many of the other conversions
> > if you wish to do this.
>
> And I would not recommend this as an "outreachy introduction task"
> unless you understand this. There are much easier first patch tasks you
> can accomplish instead.
>
Hi Greg,
I should've made this into a question for the maintainers instead of a
patch. Sorry about that. Dan's and your comments are well noted.
Thank you,
Jaehee
> good luck!
>
> greg k-h
next prev parent reply other threads:[~2022-04-13 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:14 [PATCH] staging: greybus: replace zero-element array with flexible-array Jaehee Park
2022-04-12 4:56 ` Greg Kroah-Hartman
2022-04-12 4:57 ` Greg Kroah-Hartman
2022-04-13 4:50 ` Jaehee Park [this message]
2022-04-13 7:17 ` Dan Carpenter
2022-04-12 7:24 ` Dan Carpenter
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=20220413045031.GC3357359@jaehee-ThinkPad-X1-Extreme \
--to=jhpark1013@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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