From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] omap3isp: ispqueue: Fix uninitialized variable compiler warnings
Date: Mon, 07 Jan 2013 23:23:58 +0100 [thread overview]
Message-ID: <1394965.8B914mfRsT@avalon> (raw)
In-Reply-To: <20130104225136.GI4738@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Saturday 05 January 2013 00:51:36 Sakari Ailus wrote:
> On Mon, Dec 17, 2012 at 09:52:48AM +0100, Laurent Pinchart wrote:
> > drivers/media/platform/omap3isp/ispqueue.c:399:18: warning: 'pa' may be
> > used uninitialized in this function [-Wuninitialized]
> >
> > This is a false positive but the compiler has no way to know about it,
> > so initialize the variable to 0.
> >
> > drivers/media/platform/omap3isp/ispqueue.c:445:6: warning:
> > 'vm_page_prot' may be used uninitialized in this function
> > [-Wuninitialized]
> >
> > This is a false positive and the compiler should know better. Use
> > uninitialized_var().
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >
> > drivers/media/platform/omap3isp/ispqueue.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/platform/omap3isp/ispqueue.c
> > b/drivers/media/platform/omap3isp/ispqueue.c index 15bf3ea..1388eb7
> > 100644
> > --- a/drivers/media/platform/omap3isp/ispqueue.c
> > +++ b/drivers/media/platform/omap3isp/ispqueue.c
> > @@ -366,7 +366,7 @@ static int isp_video_buffer_prepare_pfnmap(struct
> > isp_video_buffer *buf)
> > unsigned long this_pfn;
> > unsigned long start;
> > unsigned long end;
> > - dma_addr_t pa;
> > + dma_addr_t pa = 0;
>
> Why 0 and not something else arbitrary? :-)
>
> The value will not be used as far as I can tell. If it gets used it
> certainly is a bug.
If buf->vbuf.length == 0 pa will be used uninitialized. This is clearly a bug,
but I thought it would be easier to debug if pa was set to 0 in that case
instead of a random value through uninitialized_var().
> > int ret = -EFAULT;
> >
> > start = buf->vbuf.m.userptr;
> >
> > @@ -419,7 +419,7 @@ done:
> > static int isp_video_buffer_prepare_vm_flags(struct isp_video_buffer
> > *buf)
> > {
> > struct vm_area_struct *vma;
> > - pgprot_t vm_page_prot;
> > + pgprot_t uninitialized_var(vm_page_prot);
> > unsigned long start;
> > unsigned long end;
> > int ret = -EFAULT;
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-01-07 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 8:52 [PATCH] omap3isp: ispqueue: Fix uninitialized variable compiler warnings Laurent Pinchart
2013-01-04 22:51 ` Sakari Ailus
2013-01-07 22:23 ` Laurent Pinchart [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=1394965.8B914mfRsT@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.