From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Colin King <colin.king@canonical.com>
Cc: Vaibhav Agarwal <vaibhav.sr@gmail.com>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] greybus: audio: ensure module is set to avoid crash on dev_err message
Date: Fri, 23 Sep 2016 18:58:02 +0200 [thread overview]
Message-ID: <20160923165802.GA7575@kroah.com> (raw)
In-Reply-To: <20160923102540.18261-1-colin.king@canonical.com>
On Fri, Sep 23, 2016 at 11:25:40AM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently, if info is null, the dev_err message is dereferencing an
> uninitialized module pointer. Instead, initialize module before the
> dev_err call to fix this issue.
>
> Found using static analysis with cppcheck:
> [drivers/staging/greybus/audio_topology.c:175]: (error)
> Uninitialized variable: module
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/staging/greybus/audio_topology.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/greybus/audio_topology.c b/drivers/staging/greybus/audio_topology.c
> index 5eef536..c43a959 100644
> --- a/drivers/staging/greybus/audio_topology.c
> +++ b/drivers/staging/greybus/audio_topology.c
> @@ -171,6 +171,9 @@ static int gbcodec_mixer_ctl_info(struct snd_kcontrol *kcontrol,
> data = (struct gbaudio_ctl_pvt *)kcontrol->private_value;
> info = (struct gb_audio_ctl_elem_info *)data->info;
>
> + module = find_gb_module(gbcodec, kcontrol->id.name);
> + if (!module)
> + return -EINVAL;
How do you know you can get a module at this point in time, you haven't
looked at the type of info to know that?
I agree that there is an issue here, but I don't think this is the
correct fix. Vaibhav?
next prev parent reply other threads:[~2016-09-23 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 10:25 [PATCH] greybus: audio: ensure module is set to avoid crash on dev_err message Colin King
2016-09-23 16:58 ` Greg Kroah-Hartman [this message]
2016-09-23 18:20 ` Vaibhav Agarwal
2016-09-23 18:29 ` Colin Ian King
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=20160923165802.GA7575@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vaibhav.sr@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