From: Dan Carpenter <error27@gmail.com>
To: Jarod Wilson <jarod@redhat.com>, Dmitri Belimov <d.belimov@gmail.com>
Cc: linux-media@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] tm6000: fix vbuf may be used uninitialized
Date: Thu, 24 Mar 2011 23:31:08 +0300 [thread overview]
Message-ID: <20110324203108.GX2008@bicker> (raw)
In-Reply-To: <1300997220-4354-1-git-send-email-jarod@redhat.com>
On Thu, Mar 24, 2011 at 04:07:00PM -0400, Jarod Wilson wrote:
> Signed-off-by: Jarod Wilson <jarod@redhat.com>
Jarod, there is a lot of information missing from your change log... :/
> CC: devel@driverdev.osuosl.org
> ---
> drivers/staging/tm6000/tm6000-video.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/staging/tm6000/tm6000-video.c b/drivers/staging/tm6000/tm6000-video.c
> index c80a316..bfebedd 100644
> --- a/drivers/staging/tm6000/tm6000-video.c
> +++ b/drivers/staging/tm6000/tm6000-video.c
> @@ -228,7 +228,7 @@ static int copy_streams(u8 *data, unsigned long len,
> unsigned long header = 0;
> int rc = 0;
> unsigned int cmd, cpysize, pktsize, size, field, block, line, pos = 0;
> - struct tm6000_buffer *vbuf;
> + struct tm6000_buffer *vbuf = NULL;
> char *voutp = NULL;
> unsigned int linewidth;
>
This looks like a real bug versus just a GCC warning. It was introduced
in 8aff8ba95155df "[media] tm6000: add radio support to the driver".
I've added Dmitri to the CC list.
regards,
dan carpenter
next prev parent reply other threads:[~2011-03-24 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 20:07 [PATCH] tm6000: fix vbuf may be used uninitialized Jarod Wilson
2011-03-24 20:31 ` Dan Carpenter [this message]
2011-03-24 22:05 ` Jarod Wilson
2011-04-11 21:48 ` Jarod Wilson
2011-04-12 18:48 ` [PATCH v2] " Jarod Wilson
2011-04-15 2:04 ` Dmitri Belimov
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=20110324203108.GX2008@bicker \
--to=error27@gmail.com \
--cc=d.belimov@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=jarod@redhat.com \
--cc=linux-media@vger.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