From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:mirror-poly-aosp-pixel-malibu 1/1] iommufd_utils.h:649:18: error: 'struct iommu_hw_info' has no member named 'in_data_type'; did you mean 'out_data_type'?
Date: Wed, 01 Apr 2026 06:22:48 +0200 [thread overview]
Message-ID: <202604010624.EwhbbCOh-lkp@intel.com> (raw)
Hi Nicolin,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common mirror-poly-aosp-pixel-malibu
head: 9cbd7eeda1fe517f9ce3451fb3d7b4663df71429
commit: 724f6df514f78613995fb5c02463e42429942495 [1/1] iommufd/selftest: Update hw_info coverage for an input data_type
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260401/202604010624.EwhbbCOh-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260401/202604010624.EwhbbCOh-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/202604010624.EwhbbCOh-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from iommufd.c:10:
iommufd_utils.h: In function '_test_cmd_get_hw_info':
>> iommufd_utils.h:649:18: error: 'struct iommu_hw_info' has no member named 'in_data_type'; did you mean 'out_data_type'?
649 | .in_data_type = data_type,
| ^~~~~~~~~~~~
| out_data_type
>> iommufd_utils.h:655:26: error: 'IOMMU_HW_INFO_TYPE_DEFAULT' undeclared (first use in this function); did you mean 'IOMMU_HW_INFO_TYPE_SELFTEST'?
655 | if (data_type != IOMMU_HW_INFO_TYPE_DEFAULT)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| IOMMU_HW_INFO_TYPE_SELFTEST
iommufd_utils.h:655:26: note: each undeclared identifier is reported only once for each function it appears in
>> iommufd_utils.h:656:30: error: 'IOMMU_HW_INFO_FLAG_INPUT_TYPE' undeclared (first use in this function)
656 | cmd.flags |= IOMMU_HW_INFO_FLAG_INPUT_TYPE;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from iommufd_utils.h:13:
iommufd.c: In function 'iommufd_ioas_setup':
iommufd.c:230:44: error: 'MOCK_FLAGS_DEVICE_PASID' undeclared (first use in this function); did you mean 'MOCK_FLAGS_DEVICE_NO_DIRTY'?
230 | MOCK_FLAGS_DEVICE_PASID,
| ^~~~~~~~~~~~~~~~~~~~~~~
../kselftest_harness.h:758:20: note: in definition of macro '__EXPECT'
758 | __typeof__(_seen) __seen = (_seen); \
| ^~~~~
iommufd_utils.h:123:9: note: in expansion of macro 'ASSERT_EQ'
123 | ASSERT_EQ(0, _test_cmd_mock_domain_flags(self->fd, ioas_id, flags, \
| ^~~~~~~~~
iommufd.c:229:17: note: in expansion of macro 'test_cmd_mock_domain_flags'
229 | test_cmd_mock_domain_flags(self->ioas_id,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
iommufd.c: In function 'iommufd_ioas_get_hw_info':
>> iommufd.c:618:38: error: 'IOMMU_HW_INFO_TYPE_DEFAULT' undeclared (first use in this function); did you mean 'IOMMU_HW_INFO_TYPE_SELFTEST'?
618 | IOMMU_HW_INFO_TYPE_DEFAULT, NULL, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
../kselftest_harness.h:758:20: note: in definition of macro '__EXPECT'
758 | __typeof__(_seen) __seen = (_seen); \
| ^~~~~
iommufd_utils.h:701:9: note: in expansion of macro 'ASSERT_EQ'
701 | ASSERT_EQ(0, _test_cmd_get_hw_info(self->fd, device_id, data_type, \
| ^~~~~~~~~
iommufd.c:617:17: note: in expansion of macro 'test_cmd_get_hw_info'
617 | test_cmd_get_hw_info(self->device_id,
| ^~~~~~~~~~~~~~~~~~~~
iommufd.c:650:35: error: 'MOCK_PASID_WIDTH' undeclared (first use in this function)
650 | ASSERT_EQ(MOCK_PASID_WIDTH, max_pasid);
| ^~~~~~~~~~~~~~~~
../kselftest_harness.h:757:20: note: in definition of macro '__EXPECT'
757 | __typeof__(_expected) __exp = (_expected); \
| ^~~~~~~~~
iommufd.c:650:25: note: in expansion of macro 'ASSERT_EQ'
650 | ASSERT_EQ(MOCK_PASID_WIDTH, max_pasid);
| ^~~~~~~~~
iommufd.c: In function 'iommufd_dirty_tracking_device_dirty_capability':
iommufd_utils.h:711:44: error: 'IOMMU_HW_INFO_TYPE_DEFAULT' undeclared (first use in this function); did you mean 'IOMMU_HW_INFO_TYPE_SELFTEST'?
711 | IOMMU_HW_INFO_TYPE_DEFAULT, NULL, \
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
../kselftest_harness.h:758:20: note: in definition of macro '__EXPECT'
758 | __typeof__(_seen) __seen = (_seen); \
| ^~~~~
iommufd_utils.h:710:9: note: in expansion of macro 'ASSERT_EQ'
710 | ASSERT_EQ(0, _test_cmd_get_hw_info(self->fd, device_id, \
| ^~~~~~~~~
iommufd.c:1965:9: note: in expansion of macro 'test_cmd_get_hw_capabilities'
1965 | test_cmd_get_hw_capabilities(self->idev_id, caps);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
In file included from iommufd_fail_nth.c:23:
iommufd_utils.h: In function '_test_cmd_get_hw_info':
>> iommufd_utils.h:649:18: error: 'struct iommu_hw_info' has no member named 'in_data_type'; did you mean 'out_data_type'?
649 | .in_data_type = data_type,
| ^~~~~~~~~~~~
| out_data_type
>> iommufd_utils.h:655:26: error: 'IOMMU_HW_INFO_TYPE_DEFAULT' undeclared (first use in this function); did you mean 'IOMMU_HW_INFO_TYPE_SELFTEST'?
655 | if (data_type != IOMMU_HW_INFO_TYPE_DEFAULT)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| IOMMU_HW_INFO_TYPE_SELFTEST
iommufd_utils.h:655:26: note: each undeclared identifier is reported only once for each function it appears in
>> iommufd_utils.h:656:30: error: 'IOMMU_HW_INFO_FLAG_INPUT_TYPE' undeclared (first use in this function)
656 | cmd.flags |= IOMMU_HW_INFO_FLAG_INPUT_TYPE;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
iommufd_fail_nth.c: In function 'test_nth_device':
>> iommufd_fail_nth.c:615:54: error: 'IOMMU_HW_INFO_TYPE_DEFAULT' undeclared (first use in this function); did you mean 'IOMMU_HW_INFO_TYPE_SELFTEST'?
615 | if (_test_cmd_get_hw_info(self->fd, idev_id, IOMMU_HW_INFO_TYPE_DEFAULT,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| IOMMU_HW_INFO_TYPE_SELFTEST
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-01 4:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202604010624.EwhbbCOh-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.