mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>
Cc: ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ocfs2/dlm: use struct_size() helper
Date: Thu, 6 Jun 2019 06:40:00 +0800	[thread overview]
Message-ID: <9bee6ee0-ba29-ea0d-d5d2-f8c09158a1cf@linux.alibaba.com> (raw)
In-Reply-To: <20190605204926.GA24467@embeddedor>



On 19/6/6 04:49, Gustavo A. R. Silva 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 dlm_migratable_lockres 
> {
> i	...
>         struct dlm_migratable_lock ml[0];  // 16 bytes each, begins at byte 112
> };
> 
> Make use of the struct_size() helper instead of an open-coded version
> in order to avoid any potential type mistakes.
> 
> So, replace the following form:
> 
> sizeof(struct dlm_migratable_lockres) + (mres->num_locks * sizeof(struct dlm_migratable_lock))
> 
> with:
> 
> struct_size(mres, ml, mres->num_locks)
> 
> Notice that, in this case, variable sz is not necessary, hence it
> is removed.
> 
> This code was detected with the help of Coccinelle.
> 
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>

Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
>  fs/ocfs2/dlm/dlmrecovery.c | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/ocfs2/dlm/dlmrecovery.c b/fs/ocfs2/dlm/dlmrecovery.c
> index e22d6a115220..064ce5bbc3f6 100644
> --- a/fs/ocfs2/dlm/dlmrecovery.c
> +++ b/fs/ocfs2/dlm/dlmrecovery.c
> @@ -1109,7 +1109,7 @@ static int dlm_send_mig_lockres_msg(struct dlm_ctxt *dlm,
>  {
>  	u64 mig_cookie = be64_to_cpu(mres->mig_cookie);
>  	int mres_total_locks = be32_to_cpu(mres->total_locks);
> -	int sz, ret = 0, status = 0;
> +	int ret = 0, status = 0;
>  	u8 orig_flags = mres->flags,
>  	   orig_master = mres->master;
>  
> @@ -1117,9 +1117,6 @@ static int dlm_send_mig_lockres_msg(struct dlm_ctxt *dlm,
>  	if (!mres->num_locks)
>  		return 0;
>  
> -	sz = sizeof(struct dlm_migratable_lockres) +
> -		(mres->num_locks * sizeof(struct dlm_migratable_lock));
> -
>  	/* add an all-done flag if we reached the last lock */
>  	orig_flags = mres->flags;
>  	BUG_ON(total_locks > mres_total_locks);
> @@ -1133,7 +1130,8 @@ static int dlm_send_mig_lockres_msg(struct dlm_ctxt *dlm,
>  
>  	/* send it */
>  	ret = o2net_send_message(DLM_MIG_LOCKRES_MSG, dlm->key, mres,
> -				 sz, send_to, &status);
> +				 struct_size(mres, ml, mres->num_locks),
> +				 send_to, &status);
>  	if (ret < 0) {
>  		/* XXX: negative status is not handled.
>  		 * this will end up killing this node. */
> 

      reply	other threads:[~2019-06-05 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 20:49 Gustavo A. R. Silva
2019-06-05 22:40 ` Joseph Qi [this message]

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=9bee6ee0-ba29-ea0d-d5d2-f8c09158a1cf@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=jlbec@evilplan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@oss.oracle.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®