From: Hans de Goede <hdegoede@redhat.com>
To: Dongliang Mu <dzm91@hust.edu.cn>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: atomisp: move the sanity checks before variable dereferences
Date: Mon, 29 May 2023 17:46:47 +0200 [thread overview]
Message-ID: <ef8e411b-c326-9d24-c4f0-96cd183a9d1f@redhat.com> (raw)
In-Reply-To: <20230529152136.11719-1-dzm91@hust.edu.cn>
Hi,
On 5/29/23 17:21, Dongliang Mu wrote:
> Smatch reports:
>
> sh_css_load_firmware() warn: variable dereferenced before check 'fw_data'
>
> The variable fw_data can be NULL in sh_css_load_firmware, resulting in
> NULL pointer dereference.
>
> Fix this by moving the sanity checks before variable dereferences.
>
> Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
Thank you for your patch, but the same patch has already been submitted
and merged into my media-atomisp branch about a week ago:
https://git.kernel.org/pub/scm/linux/kernel/git/hansg/linux.git/commit/?h=media-atomisp&id=c09907049eea9f12e959fb88c02a483a4c5eee89
> ---
> drivers/staging/media/atomisp/pci/sh_css_firmware.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/sh_css_firmware.c b/drivers/staging/media/atomisp/pci/sh_css_firmware.c
> index e7ef578db8ab..38b757c3df0a 100644
> --- a/drivers/staging/media/atomisp/pci/sh_css_firmware.c
> +++ b/drivers/staging/media/atomisp/pci/sh_css_firmware.c
> @@ -229,6 +229,10 @@ sh_css_load_firmware(struct device *dev, const char *fw_data,
> struct sh_css_fw_bi_file_h *file_header;
> int ret;
>
> + /* some sanity checks */
> + if (!fw_data || fw_size < sizeof(struct sh_css_fw_bi_file_h))
> + return -EINVAL;
> +
> firmware_header = (struct firmware_header *)fw_data;
> file_header = &firmware_header->file_header;
> binaries = &firmware_header->binary_header;
> @@ -243,10 +247,6 @@ sh_css_load_firmware(struct device *dev, const char *fw_data,
> IA_CSS_LOG("successfully load firmware version %s", release_version);
> }
>
> - /* some sanity checks */
> - if (!fw_data || fw_size < sizeof(struct sh_css_fw_bi_file_h))
> - return -EINVAL;
> -
> if (file_header->h_size != sizeof(struct sh_css_fw_bi_file_h))
> return -EINVAL;
>
next prev parent reply other threads:[~2023-05-29 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 15:21 Dongliang Mu
2023-05-29 15:46 ` Hans de Goede [this message]
2023-05-30 1:11 ` Dongliang Mu
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=ef8e411b-c326-9d24-c4f0-96cd183a9d1f@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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®