From: Omar Sandoval <osandov@osandov.com>
To: Liu Bo <bo.liu@linux.alibaba.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: use correct args for kcalloc in btrfsic_read_block
Date: Fri, 7 Sep 2018 11:21:19 -0700	[thread overview]
Message-ID: <20180907182119.GC29245@vader> (raw)
In-Reply-To: <1536343190-400-1-git-send-email-bo.liu@linux.alibaba.com>
On Sat, Sep 08, 2018 at 01:59:50AM +0800, Liu Bo wrote:
> kcalloc is defined as
> kcalloc(size_t n, size_t size, gfp_t flags)
> 
> Although this won't cause problems in practice, btrfsic_read_block()
> has switched n with size.
> 
> This updates btrfsic_read_block() to be correct in using kcalloc.
> 
> Signed-off-by: Liu Bo <bo.liu@linux.alibaba.com>
> ---
>  fs/btrfs/check-integrity.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/btrfs/check-integrity.c b/fs/btrfs/check-integrity.c
> index 833cf3c35b4d..651b75939ce9 100644
> --- a/fs/btrfs/check-integrity.c
> +++ b/fs/btrfs/check-integrity.c
> @@ -1594,6 +1594,7 @@ static int btrfsic_read_block(struct btrfsic_state *state,
>  {
>  	unsigned int num_pages;
>  	unsigned int i;
> +	u64 size;
size_t?
Besides that, Reviewed-by: Omar Sandoval <osandov@fb.com>
>  	u64 dev_bytenr;
>  	int ret;
>  
> @@ -1608,9 +1609,8 @@ static int btrfsic_read_block(struct btrfsic_state *state,
>  
>  	num_pages = (block_ctx->len + (u64)PAGE_SIZE - 1) >>
>  		    PAGE_SHIFT;
> -	block_ctx->mem_to_free = kcalloc(sizeof(*block_ctx->datav) +
> -						sizeof(*block_ctx->pagev),
> -					 num_pages, GFP_NOFS);
> +	size = sizeof(*block_ctx->datav) + sizeof(*block_ctx->pagev);
> +	block_ctx->mem_to_free = kcalloc(num_pages, size, GFP_NOFS);
>  	if (!block_ctx->mem_to_free)
>  		return -ENOMEM;
>  	block_ctx->datav = block_ctx->mem_to_free;
> -- 
> 1.8.3.1
> 
next prev parent reply	other threads:[~2018-09-07 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 17:59 [PATCH] Btrfs: use correct args for kcalloc in btrfsic_read_block Liu Bo
2018-09-07 18:21 ` Omar Sandoval [this message]
2018-09-07 18:50   ` Liu Bo
2018-09-07 20:41 ` [PATCH v2] " Liu Bo
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=20180907182119.GC29245@vader \
    --to=osandov@osandov.com \
    --cc=bo.liu@linux.alibaba.com \
    --cc=linux-btrfs@vger.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;
as well as URLs for NNTP newsgroup(s).