From: Colin Ian King <colin.king@canonical.com>
To: Dongchun Zhu <dongchun.zhu@mediatek.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-mediatek@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: re: media: i2c: add OV02A10 image sensor driver
Date: Thu, 3 Dec 2020 18:00:20 +0000 [thread overview]
Message-ID: <9af089ea-2532-68ac-5d22-97a669ccec91@canonical.com> (raw)
Hi,
Static analysis on linux-next with Coverity has detected an issue with
the following commit:
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;
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;
559 mutex_unlock(&ov02a10->mutex);
560
561 return 0;
562
563 err_rpm_put:
564 pm_runtime_put(&client->dev);
565 unlock_and_return:
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.
Colin
next reply other threads:[~2020-12-03 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 18:00 Colin Ian King [this message]
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
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=9af089ea-2532-68ac-5d22-97a669ccec91@canonical.com \
--to=colin.king@canonical.com \
--cc=andriy.shevchenko@linux.intel.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 \
--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