linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Tomlin <atomlin@redhat.com>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
	mcgrof@kernel.org
Subject: Re: [PATCH -next] module: Use vzalloc() instead of vmalloc()/memset(0)
Date: Mon, 4 Jul 2022 15:45:18 +0100	[thread overview]
Message-ID: <20220704144518.5gjj45ldgzfl3tak@ava.usersys.com> (raw)
In-Reply-To: <20220704120337.4119910-1-yangyingliang@huawei.com>

On Mon 2022-07-04 20:03 +0800, Yang Yingliang wrote:
> Use vzalloc() instead of vmalloc() and memset(0) to simpify the code.
> 
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
>  kernel/module/main.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/kernel/module/main.c b/kernel/module/main.c
> index fed58d30725d..02b67abc448f 100644
> --- a/kernel/module/main.c
> +++ b/kernel/module/main.c
> @@ -2138,7 +2138,7 @@ static int move_module(struct module *mod, struct load_info *info)
>  
>  #ifdef CONFIG_ARCH_WANTS_MODULES_DATA_IN_VMALLOC
>  	/* Do the allocs. */
> -	ptr = vmalloc(mod->data_layout.size);
> +	ptr = vzalloc(mod->data_layout.size);
>  	/*
>  	 * The pointer to this block is stored in the module structure
>  	 * which is inside the block. Just mark it as not being a
> @@ -2151,7 +2151,6 @@ static int move_module(struct module *mod, struct load_info *info)
>  		return -ENOMEM;
>  	}
>  
> -	memset(ptr, 0, mod->data_layout.size);
>  	mod->data_layout.base = ptr;
>  #endif
>  	/* Transfer each section which specifies SHF_ALLOC */
> -- 
> 2.25.1
> 

Hi Yang,

Nice!

Reviewed-by: Aaron Tomlin <atomlin@redhat.com>


Kind regards,

-- 
Aaron Tomlin


  reply	other threads:[~2022-07-04 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 12:03 [PATCH -next] module: Use vzalloc() instead of vmalloc()/memset(0) Yang Yingliang
2022-07-04 14:45 ` Aaron Tomlin [this message]
2022-07-11 16:09 ` Luis Chamberlain

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=20220704144518.5gjj45ldgzfl3tak@ava.usersys.com \
    --to=atomlin@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=yangyingliang@huawei.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).