From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Bruce Fields <bfields@fieldses.org>,
Jeff Layton <jlayton@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] xprtrdma: Use struct_size() in kzalloc()
Date: Thu, 7 Feb 2019 21:49:06 -0600 [thread overview]
Message-ID: <f0ee151d-f4e5-ab26-1ff0-bffe1f09454d@embeddedor.com> (raw)
In-Reply-To: <07CB966E-A946-4956-8480-C0FC13E13E4E@oracle.com>
On 1/31/19 8:11 AM, Chuck Lever wrote:
>
>
>> On Jan 30, 2019, at 7:46 PM, Gustavo A. R. Silva <gustavo@embeddedor.com> wrote:
>>
>> One of the more common cases of allocation size calculations is finding
>> the size of a structure that has a zero-sized array at the end, along
>> with memory for some number of elements for that array. For example:
>>
>> struct foo {
>> int stuff;
>> struct boo entry[];
>> };
>>
>> instance = kzalloc(sizeof(struct foo) + count * sizeof(struct boo), GFP_KERNEL);
>>
>> Instead of leaving these open-coded and prone to type mistakes, we can
>> now use the new struct_size() helper:
>>
>> instance = kzalloc(struct_size(instance, entry, count), GFP_KERNEL);
>>
>> This code was detected with the help of Coccinelle.
>>
>> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>
> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
>
Thanks, Chuck.
--
Gustavo
next prev parent reply other threads:[~2019-02-08 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 0:46 [PATCH net-next] xprtrdma: Use struct_size() in kzalloc() Gustavo A. R. Silva
2019-01-31 14:11 ` Chuck Lever
2019-02-08 3:49 ` Gustavo A. R. Silva [this message]
2019-03-28 20:41 ` Gustavo A. R. Silva
2019-05-23 22:36 ` Gustavo A. R. Silva
2019-05-23 23:02 ` Chuck Lever
2019-05-23 23:32 ` David Miller
2019-05-23 23:43 ` Gustavo A. R. Silva
2019-05-28 13:56 ` Schumaker, Anna
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=f0ee151d-f4e5-ab26-1ff0-bffe1f09454d@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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).