From: David Disseldorp <ddiss@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Christian Brauner <brauner@kernel.org>
Subject: Re: [linux-next:master 11199/11507] init/initramfs_test.c:580:15: error: call to undeclared function '__override_init_fs'; ISO C99 and later do not support implicit function declarations
Date: Mon, 3 Aug 2026 14:55:12 +1000 [thread overview]
Message-ID: <20260803145512.6b2e6c18.ddiss@suse.de> (raw)
In-Reply-To: <202608010904.q5YsN4ye-lkp@intel.com>
Thanks for the report.
The vfs-7.3.misc commit da46f0e1053c9 ("initramfs_test: use test
init/exit hooks to override init fs") is bogus: it is supposed to be
applied / squashed atop Christian's ("kunit: use scoped_with_init_fs()
in tests that resolve paths") change, which includes fs_struct.h .
Christian's vfs-7.3.kthread branch has a correctly squashed version as:
b4343aebd3a4d ("initramfs_test: use test init/exit hooks to override
init fs").
@Christian: could you pleasee fix or drop the bogus da46f0e1053c9
vfs-7.3.misc commit?
Cheers, David
On Sat, 01 Aug 2026 10:26:10 +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 415606a7be939835db9b0d6b711887586646346d
> commit: da46f0e1053c98355c2d7803ff1cc46617ca81bf [11199/11507] initramfs_test: use test init/exit hooks to override init fs
> config: arm64-randconfig-001-20260801 (https://download.01.org/0day-ci/archive/20260801/202608010904.q5YsN4ye-lkp@intel.com/config)
> compiler: clang version 21.1.8 (https://github.com/llvm/llvm-project 2078da43e25a4623cab2d0d60decddf709aaea28)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260801/202608010904.q5YsN4ye-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/202608010904.q5YsN4ye-lkp@intel.com/
>
> Note: the linux-next/master HEAD 415606a7be939835db9b0d6b711887586646346d builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> >> init/initramfs_test.c:580:15: error: call to undeclared function '__override_init_fs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 580 | test->priv = __override_init_fs();
> | ^
> >> init/initramfs_test.c:580:13: error: incompatible integer to pointer conversion assigning to 'void *' from 'int' [-Wint-conversion]
> 580 | test->priv = __override_init_fs();
> | ^ ~~~~~~~~~~~~~~~~~~~~
> >> init/initramfs_test.c:586:2: error: call to undeclared function '__revert_init_fs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 586 | __revert_init_fs(test->priv);
> | ^
> 3 errors generated.
>
>
> vim +/__override_init_fs +580 init/initramfs_test.c
>
> 576
> 577 /* Tests run in a nullfs kthread; always use the init fs for path resolution. */
> 578 static int __init initramfs_test_init(struct kunit *test)
> 579 {
> > 580 test->priv = __override_init_fs();
> 581 return 0;
> 582 }
> 583
> 584 static void __init initramfs_test_exit(struct kunit *test)
> 585 {
> > 586 __revert_init_fs(test->priv);
> 587 }
> 588
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-03 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 2:26 [linux-next:master 11199/11507] init/initramfs_test.c:580:15: error: call to undeclared function '__override_init_fs'; ISO C99 and later do not support implicit function declarations kernel test robot
2026-08-03 4:55 ` David Disseldorp [this message]
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=20260803145512.6b2e6c18.ddiss@suse.de \
--to=ddiss@suse.de \
--cc=brauner@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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.