From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: gregkh@linuxfoundation.org, jslaby@suse.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: n_hdlc: Use flexible-array member
Date: Tue, 21 Jan 2020 09:24:28 -0600 [thread overview]
Message-ID: <b66589b1-7e33-70ee-6389-87ea83268bb6@embeddedor.com> (raw)
In-Reply-To: <995ff17c-81e2-15ad-c776-f07c8d61385b@embeddedor.com>
On 1/21/20 09:14, Gustavo A. R. Silva wrote:
>
>
> On 1/21/20 09:00, Mikael Magnusson wrote:
>> Gustavo Silva wrote:
>>> On 1/20/20 23:54, Jiri Slaby wrote:
>>>> On 21. 01. 20, 0:45, Gustavo A. R. Silva wrote:
>>>>> diff --git a/drivers/tty/n_hdlc.c b/drivers/tty/n_hdlc.c
>>>>> index 98361acd3053..b5499ca8757e 100644
>>>>> --- a/drivers/tty/n_hdlc.c
>>>>> +++ b/drivers/tty/n_hdlc.c
>>>>> @@ -115,7 +115,7 @@
>>>>> struct n_hdlc_buf {
>>>>> struct list_head list_item;
>>>>> int count;
>>>>> - char buf[1];
>>>>> + char buf[];
>>>>> };
>>>>>
>>>>> #define N_HDLC_BUF_SIZE (sizeof(struct n_hdlc_buf) + maxframe)
>>>>
>>>> Have you checked, that you don't have to "+ 1" here now?
>>>>
>>>
>>> Yep. That's not necessary.
>>>
>>> _In terms of memory allocation_, zero-length/one-element arrays and flexible-array
>>> members work exactly the same way.
>>
>> This is not true, but maybe it's still not necessary in this particular code, I didn't examine it.
>>
>
> I should have said _in terms of dynamic memory allocation_.
>
> Your example is correct:
>
> "... a one-element array always occupies at least as much space as a single object of the type."[1]
>
> But the above does not affect on the current code.
>
Oh wait! Yeah; I see the issue in #define N_HDLC_BUF_SIZE (sizeof(struct n_hdlc_buf) + maxframe) now...
I need to double check this.
Thanks for the feedback!
--
Gustavo
next prev parent reply other threads:[~2020-01-21 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 23:45 Gustavo A. R. Silva
2020-01-21 5:54 ` Jiri Slaby
2020-01-21 14:27 ` Gustavo A. R. Silva
2020-01-21 15:00 ` Mikael Magnusson
2020-01-21 15:14 ` Gustavo A. R. Silva
2020-01-21 15:24 ` Gustavo A. R. Silva [this message]
2020-01-21 16:03 ` Gustavo A. R. Silva
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=b66589b1-7e33-70ee-6389-87ea83268bb6@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikachu@gmail.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
all inboxes | Powered by JetHome®