[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b60e4ef2-0128-4e56-a15f-ea85194a3af0@huaweicloud.com>
Date: Mon, 21 Jul 2025 09:20:27 +0800
From: Zizhi Wo <wozizhi@...weicloud.com>
To: kernel test robot <lkp@...el.com>, viro@...iv.linux.org.uk,
jack@...e.com, brauner@...nel.org, axboe@...nel.dk, hch@....de
Cc: llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
yukuai3@...wei.com, yangerkun@...wei.com
Subject: Re: [PATCH] fs: Add additional checks for block devices during mount
在 2025/7/19 20:32, kernel test robot 写道:
> Hi Zizhi,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on brauner-vfs/vfs.all]
> [also build test ERROR on jack-fs/for_next linus/master v6.16-rc6 next-20250718]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Zizhi-Wo/fs-Add-additional-checks-for-block-devices-during-mount/20250719-105053
> base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
> patch link: https://lore.kernel.org/r/20250719024403.3452285-1-wozizhi%40huawei.com
> patch subject: [PATCH] fs: Add additional checks for block devices during mount
> config: i386-buildonly-randconfig-001-20250719 (https://download.01.org/0day-ci/archive/20250719/202507192025.N75TF4Gp-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250719/202507192025.N75TF4Gp-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@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202507192025.N75TF4Gp-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> ld.lld: error: undefined symbol: disk_live
> >>> referenced by super.c:1385 (fs/super.c:1385)
> >>> fs/super.o:(super_s_dev_test) in archive vmlinux.a
>
Sorry, disk_live() is only declared but not defined when CONFIG_BLOCK is
not set...
Perhaps, as hch suggests, it can be verified through GD_DEAD?
Thanks,
Zizhi Wo
Powered by blists - more mailing lists