mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: <cgel.zte@gmail.com>, <thierry.reding@gmail.com>, <arnd@arndb.de>
Cc: <lv.ruyi@zte.com.cn>, <linux-tegra@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH V1] firmware: tegra: fix error application of sizeof to pointer
Date: Thu, 14 Oct 2021 19:26:40 +0100	[thread overview]
Message-ID: <10dd0afe-432e-4798-1680-3edbd2b07bcb@nvidia.com> (raw)
In-Reply-To: <20211009085900.509697-1-lv.ruyi@zte.com.cn>

Hi Lv,	

On 09/10/2021 09:59, cgel.zte@gmail.com wrote:
> From: Lv Ruyi <lv.ruyi@zte.com.cn>
> 
> Application of sizeof to pointer yields the number of bytes of the pointer,
> but it should use the length of buffer in the code.
> 
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: Lv Ruyi <lv.ruyi@zte.com.cn>
> ---
>   drivers/firmware/tegra/bpmp-debugfs.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/firmware/tegra/bpmp-debugfs.c b/drivers/firmware/tegra/bpmp-debugfs.c
> index 6d66fe03fb6a..fd89899aeeed 100644
> --- a/drivers/firmware/tegra/bpmp-debugfs.c
> +++ b/drivers/firmware/tegra/bpmp-debugfs.c
> @@ -77,13 +77,14 @@ static const char *get_filename(struct tegra_bpmp *bpmp,
>   	const char *root_path, *filename = NULL;
>   	char *root_path_buf;
>   	size_t root_len;
> +	size_t root_path_buf_len = 512;
>   
> -	root_path_buf = kzalloc(512, GFP_KERNEL);
> +	root_path_buf = kzalloc(root_path_buf_len, GFP_KERNEL);
>   	if (!root_path_buf)
>   		goto out;
>   
>   	root_path = dentry_path(bpmp->debugfs_mirror, root_path_buf,
> -				sizeof(root_path_buf));
> +				root_path_buf_len);
>   	if (IS_ERR(root_path))
>   		goto out;
>   
> 

Thanks for fixing this! I just noticed that the debugfs for BPMP is 
broken on -next right now and this fixes it. We should add the fixes tag ...

Fixes: 06c2d9a078ab ("firmware: tegra: Reduce stack usage")

Otherwise ...

Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Tested-by: Jon Hunter <jonathanh@nvidia.com>

Arnd, do you want to pick this up?

Jon

-- 
nvpublic

  reply	other threads:[~2021-10-14 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-09  8:59 cgel.zte
2021-10-14 18:26 ` Jon Hunter [this message]
2021-10-14 18:31   ` Jon Hunter
2021-10-18 14:06 ` Thierry Reding
2021-12-04  8:01   ` Jon Hunter

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=10dd0afe-432e-4798-1680-3edbd2b07bcb@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=cgel.zte@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lv.ruyi@zte.com.cn \
    --cc=thierry.reding@gmail.com \
    --cc=zealci@zte.com.cn \
    /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®