From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Dongchun Zhu <dongchun.zhu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: media: i2c: add OV02A10 image sensor driver
Date: Fri, 4 Dec 2020 13:45:32 +0200 [thread overview]
Message-ID: <20201204114532.GT852@paasikivi.fi.intel.com> (raw)
In-Reply-To: <CAHp75VffBjhvuZ1Uy5Eo5qSiZ4w-+dhH5cR_XgmqGvxtrMd3uQ@mail.gmail.com>
On Thu, Dec 03, 2020 at 08:30:03PM +0200, Andy Shevchenko wrote:
> On Thu, Dec 3, 2020 at 8:24 PM Colin Ian King <colin.king@canonical.com> wrote:
> > On 03/12/2020 18:10, Andy Shevchenko wrote:
> > > On Thu, Dec 3, 2020 at 8:03 PM Colin Ian King <colin.king@canonical.com> wrote:
> > >
> > >> Static analysis on linux-next with Coverity has detected an issue with
> > >> the following commit:
> > >
> > > If you want to fix it properly, see my comments below...
> > >
> > >> 529 static int ov02a10_s_stream(struct v4l2_subdev *sd, int on)
> > >> 530 {
> > >> 531 struct ov02a10 *ov02a10 = to_ov02a10(sd);
> > >> 532 struct i2c_client *client =
> > >> v4l2_get_subdevdata(&ov02a10->subdev);
> > >>
> > >> 1. var_decl: Declaring variable ret without initializer.
> > >>
> > >> 533 int ret;
> > >> 534
> > >> 535 mutex_lock(&ov02a10->mutex);
> > >> 536
> > >>
> > >> 2. Condition ov02a10->streaming == on, taking true branch.
> > >>
> > >> 537 if (ov02a10->streaming == on)
> > >>
> > >> 3. Jumping to label unlock_and_return.
> > >>
> > >> 538 goto unlock_and_return;
> > >> 539
> > >> 540 if (on) {
> > >> 541 ret = pm_runtime_get_sync(&client->dev);
> > >> 542 if (ret < 0) {
> > >
> > >> 543 pm_runtime_put_noidle(&client->dev);
> > >> 544 goto unlock_and_return;
> > >
> > > Instead of two above:
> > > goto err_rpm_put;
> > >
> > >> 545 }
> > >> 546
> > >> 547 ret = __ov02a10_start_stream(ov02a10);
> > >> 548 if (ret) {
> > >> 549 __ov02a10_stop_stream(ov02a10);
> > >> 550 ov02a10->streaming = !on;
> > >> 551 goto err_rpm_put;
> > >> 552 }
> > >> 553 } else {
> > >> 554 __ov02a10_stop_stream(ov02a10);
> > >> 555 pm_runtime_put(&client->dev);
> > >> 556 }
> > >> 557
> > >> 558 ov02a10->streaming = on;
> > >
> > > (1)
> > >
> > >> 559 mutex_unlock(&ov02a10->mutex);
> > >> 560
> > >> 561 return 0;
> > >> 562
> > >> 563 err_rpm_put:
> > >> 564 pm_runtime_put(&client->dev);
> > >
> > >> 565 unlock_and_return:
> > >
> > > Should be moved to (1).
> > >
> > >> 566 mutex_unlock(&ov02a10->mutex);
> > >> 567
> > >>
> > >> Uninitialized scalar variable (UNINIT)
> > >> 4. uninit_use: Using uninitialized value ret.
> > >>
> > >> 568 return ret;
> > >> 569 }
> > >>
> > >> Variable ret has not been initialized, so the error return value is a
> > >> garbage value. It should be initialized with some appropriate negative
> > >> error code, or ret could be removed and the return should return a
> > >> literal value of a error code.
> > >>
> > >> I was unsure what value is appropriate to fix this, so instead I'm
> > >> reporting this issue.
> > >
> > Not sure I fully understand how that fixes it.
>
> If you are not sure and have no means to test, then don't bother. This
> is not the priority driver anyway.
Arnd sent a patch to address this:
<URL:https://patchwork.linuxtv.org/project/linux-media/patch/20201204082037.1658297-1-arnd@kernel.org/>
--
Sakari Ailus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-04 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9af089ea-2532-68ac-5d22-97a669ccec91@canonical.com>
2020-12-03 18:10 ` media: i2c: add OV02A10 image sensor driver Andy Shevchenko
2020-12-03 18:24 ` Colin Ian King
2020-12-03 18:30 ` Andy Shevchenko
2020-12-04 11:45 ` Sakari Ailus [this message]
2020-12-04 2:46 ` Dongchun Zhu
2020-12-04 6:23 ` Tomasz Figa
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=20201204114532.GT852@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=colin.king@canonical.com \
--cc=dongchun.zhu@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab+huawei@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