[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4a87c2d9-89fa-2cec-7707-08fc78c88bf8@kernel.dk>
Date: Fri, 6 May 2022 09:09:41 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Nathan Chancellor <nathan@...nel.org>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Keith Busch <kbusch@...nel.org>,
Sagi Grimberg <sagi@...mberg.me>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Tom Rix <trix@...hat.com>, Kanchan Joshi <joshi.k@...sung.com>,
Anuj Gupta <anuj20.g@...sung.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] nvme: Ensure ret is always initialized in
On 5/6/22 9:03 AM, Nathan Chancellor wrote:
> Clang warns:
>
> drivers/nvme/host/ioctl.c:674:6: error: variable 'ret' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized]
> if (ns)
> ^~
> drivers/nvme/host/ioctl.c:677:9: note: uninitialized use occurs here
> return ret;
> ^~~
> drivers/nvme/host/ioctl.c:674:2: note: remove the 'if' if its condition is always true
> if (ns)
> ^~~~~~~
> drivers/nvme/host/ioctl.c:672:9: note: initialize the variable 'ret' to silence this warning
> int ret;
> ^
> = 0
> 1 error generated.
>
> Initialize ret to zero so that it cannot be used uninitialized.
Thanks, will fold this in.
> Or alternatively, remove the 'if (ns)' if ns can never be NULL; I tried
> going down the rabbit hole to see if that is possible but I got a little
> lost :^)
For the admin queue, ns can be NULL.
--
Jens Axboe
Powered by blists - more mailing lists