On Fri, 10 May 2024 07:09:52 +0800, kernel test robot <lkp@xxxxxxxxx> wrote: > Hi Heng, > > kernel test robot noticed the following build errors: > > [auto build test ERROR on net-next/main] > > url: https://github.com/intel-lab-lkp/linux/commits/Heng-Qi/linux-dim-move-useful-macros-to-h-file/20240509-125007 > base: net-next/main > patch link: https://lore.kernel.org/r/20240509044747.101237-3-hengqi%40linux.alibaba.com > patch subject: [PATCH net-next v13 2/4] ethtool: provide customized dim profile management > config: arm-randconfig-002-20240510 (https://download.01.org/0day-ci/archive/20240510/202405100654.5PbLQXnL-lkp@xxxxxxxxx/config) > compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project b910bebc300dafb30569cecc3017b446ea8eafa0) > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240510/202405100654.5PbLQXnL-lkp@xxxxxxxxx/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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202405100654.5PbLQXnL-lkp@xxxxxxxxx/ > > All errors (new ones prefixed by >>): > > >> ld.lld: error: undefined symbol: lockdep_rtnl_is_held This failed use case seems to come from this series triggering a problem that has not been triggered historically, namely lockdep_rtnl_is_held() is not called in an environment where CONFIG_NET is not configured and CONFIG_PROVE_LOCKING is configured: If CONFIG_PROVE_LOCKING is configured as Y and CONFIG_NET is n, then lockdep_rtnl_is_held is in an undefined state at this time. So I think we should declare "CONFIG_PROVE_LOCKING depends on CONFIG_NET". How do you think? Thanks! > >>> referenced by net_dim.c > >>> lib/dim/net_dim.o:(net_dim_free_irq_moder) in archive vmlinux.a > >>> referenced by net_dim.c > >>> lib/dim/net_dim.o:(net_dim_free_irq_moder) in archive vmlinux.a > > -- > 0-DAY CI Kernel Test Service > https://github.com/intel/lkp-tests/wiki
