From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] DaVinci-VPFE-Capture: fix error handling
Date: Wed, 23 Nov 2016 19:24:11 +0100 [thread overview]
Message-ID: <a1677e94-24f3-c745-ca36-53b1e29955e4@users.sourceforge.net> (raw)
In-Reply-To: <20161122205231.799066-1-arnd@arndb.de>
> A recent cleanup had the right idea to remove the initialization
> of the error variable, but missed the actual benefit of that,
> which is that we get warnings if there is a bug in it.
> Now we get a warning about a bug that was introduced by this cleanup:
>
> drivers/media/platform/davinci/vpfe_capture.c: In function 'vpfe_probe':
> drivers/media/platform/davinci/vpfe_capture.c:1992:9: error: 'ret' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Thanks for your information.
> This adds the missing initialization that the warning is about,
I have got the impression that an other wording would be more appropriate.
> and another one that was preexisting and that we did not get
> a warning for. That second bug has existed since the driver
> was first added.
Do you distinguish better between the setting for two return values because of either
a memory allocation failure and a failed call of the function "v4l2_i2c_new_subdev_board" here?
> Fixes: efb74461f5a6 ("[media] DaVinci-VPFE-Capture: Delete an unnecessary variable initialisation in vpfe_probe()")
> Fixes: 7da8a6cb3e5b ("V4L/DVB (12248): v4l: vpfe capture bridge driver for DM355 and DM6446")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/media/platform/davinci/vpfe_capture.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/davinci/vpfe_capture.c b/drivers/media/platform/davinci/vpfe_capture.c
> index 6c41782b3ba0..ee1cd79739c8 100644
> --- a/drivers/media/platform/davinci/vpfe_capture.c
> +++ b/drivers/media/platform/davinci/vpfe_capture.c
> @@ -1847,8 +1847,10 @@ static int vpfe_probe(struct platform_device *pdev)
>
> /* Allocate memory for ccdc configuration */
> ccdc_cfg = kmalloc(sizeof(*ccdc_cfg), GFP_KERNEL);
> - if (!ccdc_cfg)
> + if (!ccdc_cfg) {
> + ret = -ENOMEM;
> goto probe_free_dev_mem;
> + }
>
> mutex_lock(&ccdc_lock);
>
> @@ -1964,6 +1966,7 @@ static int vpfe_probe(struct platform_device *pdev)
> v4l2_info(&vpfe_dev->v4l2_dev,
> "v4l2 sub device %s register fails\n",
> sdinfo->name);
> + ret = -ENXIO;
> goto probe_sd_out;
> }
> }
>
Thanks for your source code correction.
Regards,
Markus
prev parent reply other threads:[~2016-11-23 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 20:52 [PATCH] [media] DaVinci-VPFE-Capture: fix error handling Arnd Bergmann
2016-11-23 18:24 ` SF Markus Elfring [this message]
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=a1677e94-24f3-c745-ca36-53b1e29955e4@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=arnd@arndb.de \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.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