[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e5e557bf-53b9-49ca-9bd7-3dfe85ccbbb8@stanley.mountain>
Date: Mon, 7 Apr 2025 11:56:13 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Maxime Ripard <mripard@...nel.org>
Cc: sunliming@...ux.dev, dave.stevenson@...pberrypi.com, mcanal@...lia.com,
kernel-list@...pberrypi.com, maarten.lankhorst@...ux.intel.com,
tzimmermann@...e.de, airlied@...il.com, simona@...ll.ch,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
sunliming <sunliming@...inos.cn>, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] drm/vc4: fix uninitialized smatch warnings
On Mon, Apr 07, 2025 at 09:13:59AM +0200, Maxime Ripard wrote:
> On Sat, Apr 05, 2025 at 10:45:03AM +0800, sunliming@...ux.dev wrote:
> > From: sunliming <sunliming@...inos.cn>
> >
> > Fix below smatch warnings:
> > drivers/gpu/drm/vc4/vc4_gem.c:604 vc4_lock_bo_reservations() error: uninitialized symbol 'ret'.
> >
> > Reported-by: kernel test robot <lkp@...el.com>
> > Reported-by: Dan Carpenter <dan.carpenter@...aro.org>
> > Closes: https://lore.kernel.org/r/202504021500.3AM1hKKS-lkp@intel.com/
> > Signed-off-by: sunliming <sunliming@...inos.cn>
> > ---
> > drivers/gpu/drm/vc4/vc4_gem.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/vc4/vc4_gem.c b/drivers/gpu/drm/vc4/vc4_gem.c
> > index 8125f87edc60..04ea1696fc5d 100644
> > --- a/drivers/gpu/drm/vc4/vc4_gem.c
> > +++ b/drivers/gpu/drm/vc4/vc4_gem.c
> > @@ -582,7 +582,7 @@ static int
> > vc4_lock_bo_reservations(struct vc4_exec_info *exec,
> > struct drm_exec *exec_ctx)
> > {
> > - int ret;
> > + int ret = 0;
> >
> > /* Reserve space for our shared (read-only) fence references,
> > * before we commit the CL to the hardware.
>
> I don't see a code path where ret is used without being initialized. Can
> you clarify that in the commit log?
Apparently the drm_exec_until_all_locked() loop always iterates at least
once. If you have the cross function database then this is parsed
automatically, but I've also hard coded it as a loop at least once macro
just a 1 minute ago to silence this false positive.s
regards,
dan carpenter
Powered by blists - more mailing lists