Nicolin Chen 9a96876e3c iommufd/selftest: Fix build warnings due to uninitialized mfd ... Commit 869c788909 ("selftests: harness: Stop using setjmp()/longjmp()") changed the harness structure. For some unknown reason, two build warnings occur to the iommufd selftest: iommufd.c: In function ‘wrapper_iommufd_mock_domain_all_aligns’: iommufd.c:1807:17: warning: ‘mfd’ may be used uninitialized in this function 1807 | close(mfd); | ^~~~~~~~~~ iommufd.c:1767:13: note: ‘mfd’ was declared here 1767 | int mfd; | ^~~ iommufd.c: In function ‘wrapper_iommufd_mock_domain_all_aligns_copy’: iommufd.c:1870:17: warning: ‘mfd’ may be used uninitialized in this function 1870 | close(mfd); | ^~~~~~~~~~ iommufd.c:1819:13: note: ‘mfd’ was declared here 1819 | int mfd; | ^~~ All the mfd have been used in the variant->file path only, so it's likely a false alarm. FWIW, the commit mentioned above does not cause this, yet it might affect gcc in a certain way that resulted in the warnings. It is also found that ading a dummy setjmp (which doesn't make sense) could mute the warnings: https://lore.kernel.org/all/aEi8DV+ReF3v3Rlf@nvidia.com/ The job of this selftest is to catch kernel bug, while such warnings will unlikely disrupt its role. Mute the warning by force initializing the mfd and add an ASSERT_GT(). Link: https://patch.msgid.link/r/6951d85d5cd34cbf22abab7714542654e63ecc44.1750787928.git.nicolinc@nvidia.com Reviewed-by: Jason Gunthorpe <jgg@nvidia.com> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>		2025-06-24 15:45:13 -03:00
..
.gitignore	…
Makefile	iommufd: IOMMU_IOAS_CHANGE_PROCESS selftest	2024-11-14 13:42:35 -04:00
config	…
iommufd.c	iommufd/selftest: Fix build warnings due to uninitialized mfd	2025-06-24 15:45:13 -03:00
iommufd_fail_nth.c	iommufd/selftest: Add coverage for reporting max_pasid_log2 via IOMMU_HW_INFO	2025-03-28 10:07:23 -03:00
iommufd_utils.h	iommufd/selftest: Add missing close(mfd) in memfd_mmap()	2025-06-24 15:45:12 -03:00