From: Pavel Begunkov <asml.silence@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [axboe-block:for-6.15/io_uring 55/56] io_uring/net.c:719:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is true
Date: Thu, 27 Feb 2025 10:07:13 +0000 [thread overview]
Message-ID: <5f2ede96-183a-4dc7-94b5-d4ec00d38c08@gmail.com> (raw)
In-Reply-To: <202502270853.xYltEB97-lkp@intel.com>
On 2/27/25 00:12, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-6.15/io_uring
> head: 7eb5bb749ed945ead6a089e18e1d1da74523ac9a
> commit: 68525267875757520752ff1abbda0af58fc172b9 [55/56] io_uring/net: unify *mshot_prep calls with compat
> config: um-randconfig-001-20250227 (https://download.01.org/0day-ci/archive/20250227/202502270853.xYltEB97-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502270853.xYltEB97-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202502270853.xYltEB97-lkp@intel.com/
Not a real problem, it's just the compiler (understandably) can't
derive that the block is only empty IFF io_is_compat() is a
constant false.
We can initialise the var and let the compiler optimise it to
silence the warning.
--
Pavel Begunkov
prev parent reply other threads:[~2025-02-27 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 0:12 [axboe-block:for-6.15/io_uring 55/56] io_uring/net.c:719:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is true kernel test robot
2025-02-27 10:07 ` Pavel Begunkov [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=5f2ede96-183a-4dc7-94b5-d4ec00d38c08@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.