From: Marc Zyngier <maz@kernel.org>
To: Quentin Perret <qperret@google.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
kvmarm <kvmarm@lists.linux.dev>,
Oliver Upton <oliver.upton@linux.dev>
Subject: Re: [kvmarm:fixes 18/18] arch/arm64/kvm/hyp/nvhe/mem_protect.c:1086:9: warning: variable 'ret' is uninitialized when used here
Date: Mon, 10 Feb 2025 10:37:03 +0000 [thread overview]
Message-ID: <867c5yt7ao.wl-maz@kernel.org> (raw)
In-Reply-To: <Z6nKYtyJO2bNycJw@google.com>
On Mon, 10 Feb 2025 09:44:02 +0000,
Quentin Perret <qperret@google.com> wrote:
>
> On Monday 10 Feb 2025 at 09:21:29 (+0000), Marc Zyngier wrote:
> > On Mon, 10 Feb 2025 01:39:04 +0000,
> > kernel test robot <lkp@intel.com> wrote:
> > >
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git fixes
> > > head: eabc7aaef7a553b64bf6e631ce04526af6c8d104
> > > commit: eabc7aaef7a553b64bf6e631ce04526af6c8d104 [18/18] KVM: arm64: Simplify np-guest hypercalls
> > > config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20250210/202502100911.8c9DbtKD-lkp@intel.com/config)
> > > compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250210/202502100911.8c9DbtKD-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/202502100911.8c9DbtKD-lkp@intel.com/
> > >
> > > All warnings (new ones prefixed by >>):
> > >
> > > >> arch/arm64/kvm/hyp/nvhe/mem_protect.c:1086:9: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
> > > 1086 | return ret;
> > > | ^~~
> > > arch/arm64/kvm/hyp/nvhe/mem_protect.c:1076:9: note: initialize the variable 'ret' to silence this warning
> > > 1076 | int ret;
> > > | ^
> > > | = 0
> > > 1 warning generated.
> >
> > Nice catch. I wish the compiler would warn for these by default...
>
> So do I...
>
> > Quentin, are you happy with the following patch that I can stash on
> > top of the current set of fixes?
>
> Absolutely, thanks for the patch and sorry the mess!
>
> Reviewed-by: Quentin Perret <qperret@google.com>
Now queued and pushed out.
LKP people: please fix the mailing address you are using, as it
changed over two years ago, and you're still using the old one.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-02-10 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 1:39 [kvmarm:fixes 18/18] arch/arm64/kvm/hyp/nvhe/mem_protect.c:1086:9: warning: variable 'ret' is uninitialized when used here kernel test robot
2025-02-10 9:21 ` Marc Zyngier
2025-02-10 9:44 ` Quentin Perret
2025-02-10 10:37 ` Marc Zyngier [this message]
2025-02-13 7:25 ` Philip Li
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=867c5yt7ao.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
/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