From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alessandro Zanni <alessandro.zanni87@gmail.com>
Cc: kevin.tian@intel.com, shuah@kernel.org, iommu@lists.linux.dev,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests/iommu: prevent use of uninitialized variable
Date: Fri, 26 Sep 2025 10:02:37 -0300 [thread overview]
Message-ID: <20250926130237.GA2695987@ziepe.ca> (raw)
In-Reply-To: <20250924171629.50266-1-alessandro.zanni87@gmail.com>
On Wed, Sep 24, 2025 at 07:16:28PM +0200, Alessandro Zanni wrote:
> Fix to avoid the usage of the `res` variable uninitialized in the
> following macro expansions.
>
> It solves the following warning:
> In function ‘iommufd_viommu_vdevice_alloc’,
> inlined from ‘wrapper_iommufd_viommu_vdevice_alloc’ at
> iommufd.c:2889:1:
> ../kselftest_harness.h:760:12: warning: ‘ret’ may be used uninitialized
> [-Wmaybe-uninitialized]
> 760 | if (!(__exp _t __seen)) { \
> | ^
> ../kselftest_harness.h:513:9: note: in expansion of macro ‘__EXPECT’
> 513 | __EXPECT(expected, #expected, seen, #seen, ==, 1)
> | ^~~~~~~~
> iommufd_utils.h:1057:9: note: in expansion of macro ‘ASSERT_EQ’
> 1057 | ASSERT_EQ(0, _test_cmd_trigger_vevents(self->fd, dev_id,
> nvevents))
> | ^~~~~~~~~
> iommufd.c:2924:17: note: in expansion of macro
> ‘test_cmd_trigger_vevents’
> 2924 | test_cmd_trigger_vevents(dev_id, 3);
> | ^~~~~~~~~~~~~~~~~~~~~~~~
Shouldn't word wrap output like this, ignore the checkpatch warnings.
> The issue can be reproduced, building the tests, with the command:
> make -C tools/testing/selftests TARGETS=iommu
Fixes: 97717a1f283f ("iommufd/selftest: Add IOMMU_VEVENTQ_ALLOC test coverage")
Applied, thanks
Jason
prev parent reply other threads:[~2025-09-26 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 17:16 [PATCH v2] selftests/iommu: prevent use of uninitialized variable Alessandro Zanni
2025-09-26 13:02 ` Jason Gunthorpe [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=20250926130237.GA2695987@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alessandro.zanni87@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/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