From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: jorge.lopez2@hp.com, hdegoede@redhat.com, markgross@kernel.org,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] platform/x86: hp-bioscfg: Remove useless else
Date: Fri, 11 Aug 2023 11:04:17 +0300 (EEST) [thread overview]
Message-ID: <2ec499b-c37e-0a9-c163-2a1591b56029@linux.intel.com> (raw)
In-Reply-To: <20230811062957.82728-1-jiapeng.chong@linux.alibaba.com>
On Fri, 11 Aug 2023, Jiapeng Chong wrote:
> The assignment of the else and if branches is the same, so the else
> here is redundant, so we remove it.
>
> ./drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c:545:3-5: WARNING: possible condition with no effect (if == else).
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> .../platform/x86/hp/hp-bioscfg/passwdobj-attributes.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c b/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c
> index 03d0188804ba..771e554182dc 100644
> --- a/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c
> +++ b/drivers/platform/x86/hp/hp-bioscfg/passwdobj-attributes.c
> @@ -541,14 +541,8 @@ void hp_exit_password_attributes(void)
> struct kobject *attr_name_kobj =
> bioscfg_drv.password_data[instance_id].attr_name_kobj;
>
> - if (attr_name_kobj) {
> - if (!strcmp(attr_name_kobj->name, SETUP_PASSWD))
> - sysfs_remove_group(attr_name_kobj,
> - &password_attr_group);
> - else
> - sysfs_remove_group(attr_name_kobj,
> - &password_attr_group);
> - }
> + if (attr_name_kobj)
> + sysfs_remove_group(attr_name_kobj, &password_attr_group);
> }
> bioscfg_drv.password_instances_count = 0;
> kfree(bioscfg_drv.password_data);
While this is a valid observation, I wonder why you didn't change the
create side too?
I hope it's not because you never took a look to understand the
SETUP_PASSWD related code, it'd be pretty impossible to not notice it.
This could have just as well have been a bug with inconsitent pairing
against create side, which is why reports from automated tools must not be
implemented blindly but the related code must be understood first.
--
i.
next prev parent reply other threads:[~2023-08-11 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 6:29 [PATCH] platform/x86: hp-bioscfg: Remove useless else Jiapeng Chong
2023-08-11 8:04 ` Ilpo Järvinen [this message]
2023-08-11 15:41 ` Lopez, Jorge A (Security)
2023-08-11 15:42 ` Lopez, Jorge A (Security)
-- strict thread matches above, loose matches on Subject: below --
2024-01-03 2:17 Jiapeng Chong
2024-01-03 11:53 ` Ilpo Järvinen
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=2ec499b-c37e-0a9-c163-2a1591b56029@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=abaci@linux.alibaba.com \
--cc=hdegoede@redhat.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=jorge.lopez2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@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