linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
	Christoph Lameter <cl@linux.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] percpu: convert flexible array initializers to use struct_size()
Date: Fri, 30 Oct 2020 16:38:37 -0500	[thread overview]
Message-ID: <04b2a0ec-4b2e-60d2-5f7b-26d07b93a88d@embeddedor.com> (raw)
In-Reply-To: <20201030205846.1105106-1-dennis@kernel.org>



On 10/30/20 15:58, Dennis Zhou wrote:
> Use the safer macro as sparked by the long discussion in [1].
> 
> [1] https://lore.kernel.org/lkml/20200917204514.GA2880159@google.com/
> 
> Signed-off-by: Dennis Zhou <dennis@kernel.org>

Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>

Thanks
--
Gustavo

> ---
> I'll apply it to for-5.10-fixes.
> 
>  mm/percpu.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/mm/percpu.c b/mm/percpu.c
> index 66a93f096394..ad7a37ee74ef 100644
> --- a/mm/percpu.c
> +++ b/mm/percpu.c
> @@ -1315,8 +1315,8 @@ static struct pcpu_chunk * __init pcpu_alloc_first_chunk(unsigned long tmp_addr,
>  	region_size = ALIGN(start_offset + map_size, lcm_align);
>  
>  	/* allocate chunk */
> -	alloc_size = sizeof(struct pcpu_chunk) +
> -		BITS_TO_LONGS(region_size >> PAGE_SHIFT) * sizeof(unsigned long);
> +	alloc_size = struct_size(chunk, populated,
> +				 BITS_TO_LONGS(region_size >> PAGE_SHIFT));
>  	chunk = memblock_alloc(alloc_size, SMP_CACHE_BYTES);
>  	if (!chunk)
>  		panic("%s: Failed to allocate %zu bytes\n", __func__,
> @@ -2521,8 +2521,8 @@ void __init pcpu_setup_first_chunk(const struct pcpu_alloc_info *ai,
>  	pcpu_unit_pages = ai->unit_size >> PAGE_SHIFT;
>  	pcpu_unit_size = pcpu_unit_pages << PAGE_SHIFT;
>  	pcpu_atom_size = ai->atom_size;
> -	pcpu_chunk_struct_size = sizeof(struct pcpu_chunk) +
> -		BITS_TO_LONGS(pcpu_unit_pages) * sizeof(unsigned long);
> +	pcpu_chunk_struct_size = struct_size(chunk, populated,
> +					     BITS_TO_LONGS(pcpu_unit_pages));
>  
>  	pcpu_stats_save_ai(ai);
>  
> 


      reply	other threads:[~2020-10-30 22:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 20:58 Dennis Zhou
2020-10-30 21:38 ` Gustavo A. R. Silva [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=04b2a0ec-4b2e-60d2-5f7b-26d07b93a88d@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=cl@linux.com \
    --cc=dennis@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tj@kernel.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