From: Viresh Kumar <viresh.kumar@linaro.org> To: Jian Dong <dj0227@163.com> Cc: vireshk@kernel.org, johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org, greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, huyue2@yulong.com, Jian Dong <dongjian@yulong.com> Subject: Re: [PATCH] staging: greybus: fix fw is NULL but dereferenced Date: Thu, 25 Mar 2021 16:21:55 +0530 [thread overview] Message-ID: <20210325105155.c52zc7mswoh33yjz@vireshk-i7> (raw) In-Reply-To: <1616667566-58997-1-git-send-email-dj0227@163.com> On 25-03-21, 18:19, Jian Dong wrote: > From: Jian Dong <dongjian@yulong.com> > > fixes coccicheck Error: > > drivers/staging/greybus/bootrom.c:301:41-45: ERROR: > fw is NULL but dereferenced. > > if procedure goto label directly, ret will be nefative, so the fw is NULL > and the if(condition) end with dereferenced fw. let's fix it. No, fw is accessed only for !ret case. > Signed-off-by: Jian Dong <dongjian@yulong.com> > --- > drivers/staging/greybus/bootrom.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/staging/greybus/bootrom.c b/drivers/staging/greybus/bootrom.c > index a8efb86..0439efa 100644 > --- a/drivers/staging/greybus/bootrom.c > +++ b/drivers/staging/greybus/bootrom.c > @@ -246,7 +246,7 @@ static int gb_bootrom_get_firmware(struct gb_operation *op) > struct gb_bootrom_get_firmware_response *firmware_response; > struct device *dev = &op->connection->bundle->dev; > unsigned int offset, size; > - enum next_request_type next_request; > + enum next_request_type next_request = NEXT_REQ_GET_FIRMWARE; > int ret = 0; > > /* Disable timeouts */ > @@ -298,10 +298,10 @@ static int gb_bootrom_get_firmware(struct gb_operation *op) > > queue_work: > /* Refresh timeout */ > - if (!ret && (offset + size == fw->size)) > - next_request = NEXT_REQ_READY_TO_BOOT; > - else > + if (!!ret) > next_request = NEXT_REQ_GET_FIRMWARE; > + else if (offset + size == fw->size) > + next_request = NEXT_REQ_READY_TO_BOOT; > > gb_bootrom_set_timeout(bootrom, next_request, NEXT_REQ_TIMEOUT_MS); The code is fine AFAICT, the coccicheck is buggy as it is detecting a bug here. -- viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org> To: Jian Dong <dj0227@163.com> Cc: devel@driverdev.osuosl.org, elder@kernel.org, vireshk@kernel.org, johan@kernel.org, linux-kernel@vger.kernel.org, greybus-dev@lists.linaro.org, huyue2@yulong.com, gregkh@linuxfoundation.org, Jian Dong <dongjian@yulong.com> Subject: Re: [PATCH] staging: greybus: fix fw is NULL but dereferenced Date: Thu, 25 Mar 2021 16:21:55 +0530 [thread overview] Message-ID: <20210325105155.c52zc7mswoh33yjz@vireshk-i7> (raw) In-Reply-To: <1616667566-58997-1-git-send-email-dj0227@163.com> On 25-03-21, 18:19, Jian Dong wrote: > From: Jian Dong <dongjian@yulong.com> > > fixes coccicheck Error: > > drivers/staging/greybus/bootrom.c:301:41-45: ERROR: > fw is NULL but dereferenced. > > if procedure goto label directly, ret will be nefative, so the fw is NULL > and the if(condition) end with dereferenced fw. let's fix it. No, fw is accessed only for !ret case. > Signed-off-by: Jian Dong <dongjian@yulong.com> > --- > drivers/staging/greybus/bootrom.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/staging/greybus/bootrom.c b/drivers/staging/greybus/bootrom.c > index a8efb86..0439efa 100644 > --- a/drivers/staging/greybus/bootrom.c > +++ b/drivers/staging/greybus/bootrom.c > @@ -246,7 +246,7 @@ static int gb_bootrom_get_firmware(struct gb_operation *op) > struct gb_bootrom_get_firmware_response *firmware_response; > struct device *dev = &op->connection->bundle->dev; > unsigned int offset, size; > - enum next_request_type next_request; > + enum next_request_type next_request = NEXT_REQ_GET_FIRMWARE; > int ret = 0; > > /* Disable timeouts */ > @@ -298,10 +298,10 @@ static int gb_bootrom_get_firmware(struct gb_operation *op) > > queue_work: > /* Refresh timeout */ > - if (!ret && (offset + size == fw->size)) > - next_request = NEXT_REQ_READY_TO_BOOT; > - else > + if (!!ret) > next_request = NEXT_REQ_GET_FIRMWARE; > + else if (offset + size == fw->size) > + next_request = NEXT_REQ_READY_TO_BOOT; > > gb_bootrom_set_timeout(bootrom, next_request, NEXT_REQ_TIMEOUT_MS); The code is fine AFAICT, the coccicheck is buggy as it is detecting a bug here. -- viresh _______________________________________________ devel mailing list devel@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2021-03-25 10:52 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-25 10:19 [PATCH] staging: greybus: fix fw is NULL but dereferenced Jian Dong 2021-03-25 10:19 ` Jian Dong 2021-03-25 10:29 ` Greg KH 2021-03-25 10:29 ` Greg KH 2021-03-25 11:03 ` Jian Dong 2021-03-25 11:03 ` Jian Dong 2021-03-25 11:32 ` Greg KH 2021-03-25 11:32 ` Greg KH 2021-03-25 10:50 ` Dan Carpenter 2021-03-25 10:50 ` Dan Carpenter 2021-03-25 10:51 ` Viresh Kumar [this message] 2021-03-25 10:51 ` Viresh Kumar -- strict thread matches above, loose matches on Subject: below -- 2020-01-26 8:31 Saurav Girepunje 2020-01-26 8:31 ` Saurav Girepunje 2020-01-26 11:04 ` Johan Hovold 2020-01-26 11:04 ` Johan Hovold 2020-01-26 18:30 ` Greg KH 2020-01-26 18:30 ` Greg KH
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=20210325105155.c52zc7mswoh33yjz@vireshk-i7 \ --to=viresh.kumar@linaro.org \ --cc=devel@driverdev.osuosl.org \ --cc=dj0227@163.com \ --cc=dongjian@yulong.com \ --cc=elder@kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=greybus-dev@lists.linaro.org \ --cc=huyue2@yulong.com \ --cc=johan@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=vireshk@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.