All of lore.kernel.org
 help / color / mirror / Atom feed
* [superm1:superm1/lockdown-iommu 3/3] security/lockdown/lockdown.c:217:22: error: implicit declaration of function 'iommu_is_available'; did you mean 'slab_is_available'?
@ 2026-10-28  1:14 kernel test robot
  0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2026-10-28  1:14 UTC (permalink / raw)
  To: Mario Limonciello (AMD); +Cc: oe-kbuild-all

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git superm1/lockdown-iommu
head:   74b0183524154e17897a7789da06a937eaf8b2b7
commit: 74b0183524154e17897a7789da06a937eaf8b2b7 [3/3] security: lockdown: Prevent boot with lockdown but no IOMMU
config: openrisc-randconfig-r2300-20261027 (https://download.01.org/0day-ci/archive/20261028/202610280255.TUeB5M0I-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.5.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261028/202610280255.TUeB5M0I-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/202610280255.TUeB5M0I-lkp@intel.com/

All errors (new ones prefixed by >>):

   security/lockdown/lockdown.c: In function 'lockdown_check_iommu':
>> security/lockdown/lockdown.c:217:22: error: implicit declaration of function 'iommu_is_available'; did you mean 'slab_is_available'? [-Werror=implicit-function-declaration]
     217 |                 if (!iommu_is_available()) {
         |                      ^~~~~~~~~~~~~~~~~~
         |                      slab_is_available
   cc1: some warnings being treated as errors


vim +217 security/lockdown/lockdown.c

   197	
   198	/*
   199	 * Late init call to verify IOMMU availability when lockdown is active.
   200	 * This catches cases where:
   201	 *  - IOMMU hardware is absent on the platform
   202	 *  - IOMMU was disabled by driver initialization failure
   203	 *  - IOMMU was not detected (e.g. broken firmware, missing ACPI tables)
   204	 *
   205	 * On x86, we also check no_iommu here as a double-check. The early check
   206	 * in lockdown_lsm_init() catches 'iommu=off' from the cmdline before
   207	 * lockdown_lsm_init() runs, but this late check covers any missed cases.
   208	 */
   209	static int __init lockdown_check_iommu(void)
   210	{
   211		if (kernel_locked_down > LOCKDOWN_NONE) {
   212			/*
   213			 * Check generic IOMMU availability (all architectures).
   214			 * iommu_is_available() returns true if any IOMMU driver
   215			 * registered successfully.
   216			 */
 > 217			if (!iommu_is_available()) {

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-10-28  1:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-28  1:14 [superm1:superm1/lockdown-iommu 3/3] security/lockdown/lockdown.c:217:22: error: implicit declaration of function 'iommu_is_available'; did you mean 'slab_is_available'? kernel test robot

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.