From: Paul Cercueil <paul@crapouillou.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [bug report] hwmon: Add "label" attribute
Date: Thu, 27 Jan 2022 09:47:17 +0000 [thread overview]
Message-ID: <TI4D6R.WEHYEPI3R49G3@crapouillou.net> (raw)
In-Reply-To: <20220127085245.GF25644@kili>
Hi,
Le jeu., janv. 27 2022 at 11:52:45 +0300, Dan Carpenter
<dan.carpenter@oracle.com> a écrit :
> Hello Paul Cercueil,
>
> This is a semi-automatic email about new static checker warnings.
>
> The patch 073c3ea6c530: "hwmon: Add "label" attribute" from Jan 10,
> 2022, leads to the following Smatch complaint:
>
> drivers/hwmon/hwmon.c:825 __hwmon_device_register()
> warn: variable dereferenced before check 'dev' (see line 810)
>
> drivers/hwmon/hwmon.c
> 809
> 810 if (device_property_present(dev, "label")) {
> ^^^
> The patch adds a new unchecked dereference
I will send a patch to address that.
I'm surprised that this function can be called with dev == NULL in the
first place, though.
Cheers,
-Paul
> 811 err = device_property_read_string(dev, "label", &label);
> 812 if (err < 0)
> 813 goto free_hwmon;
> 814
> 815 hwdev->label = kstrdup(label, GFP_KERNEL);
> 816 if (hwdev->label == NULL) {
> 817 err = -ENOMEM;
> 818 goto free_hwmon;
> 819 }
> 820 }
> 821
> 822 hwdev->name = name;
> 823 hdev->class = &hwmon_class;
> 824 hdev->parent = dev;
> 825 hdev->of_node = dev ? dev->of_node : NULL;
> ^^^
> Existing code checked for NULL
>
> 826 hwdev->chip = chip;
> 827 dev_set_drvdata(hdev, drvdata);
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2022-01-27 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 8:52 [bug report] hwmon: Add "label" attribute Dan Carpenter
2022-01-27 9:47 ` Paul Cercueil [this message]
2022-01-27 14:28 ` Guenter Roeck
2022-01-27 16:43 ` Paul Cercueil
2022-01-27 17:17 ` Guenter Roeck
2022-01-31 16:27 ` [PATCH] hwmon: Fix possible NULL pointer Paul Cercueil
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=TI4D6R.WEHYEPI3R49G3@crapouillou.net \
--to=paul@crapouillou.net \
--cc=dan.carpenter@oracle.com \
--cc=linux-hwmon@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