From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH/RFC 1/2] init/initramfs.c: allow asynchronous unpacking
Date: Thu, 25 Feb 2021 06:09:27 +0800 [thread overview]
Message-ID: <202102250602.pN7AGbYf-lkp@intel.com> (raw)
In-Reply-To: <20210224142909.2092914-2-linux@rasmusvillemoes.dk>
[-- Attachment #1: Type: text/plain, Size: 3660 bytes --]
Hi Rasmus,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linus/master]
[also build test ERROR on v5.11]
[cannot apply to linux/master driver-core/driver-core-testing next-20210224]
[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]
url: https://github.com/0day-ci/linux/commits/Rasmus-Villemoes/background-initramfs-unpacking-and-CONFIG_MODPROBE_PATH/20210224-232842
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git c03c21ba6f4e95e406a1a7b4c34ef334b977c194
config: alpha-randconfig-r002-20210223 (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/e7d2b5f4883ef07e135fad4e0f2340b116c65b06
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Rasmus-Villemoes/background-initramfs-unpacking-and-CONFIG_MODPROBE_PATH/20210224-232842
git checkout e7d2b5f4883ef07e135fad4e0f2340b116c65b06
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=alpha
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
>> init/initramfs.c:533:42: error: 'CONFIG_INITRAMFS_ASYNC' undeclared here (not in a function); did you mean 'CONFIG_INITRAMFS_SOURCE'?
533 | static bool __initdata initramfs_async = CONFIG_INITRAMFS_ASYNC;
| ^~~~~~~~~~~~~~~~~~~~~~
| CONFIG_INITRAMFS_SOURCE
>> init/initramfs.c:545:6: warning: no previous prototype for '_wait_for_initramfs' [-Wmissing-prototypes]
545 | void _wait_for_initramfs(const char *caller)
| ^~~~~~~~~~~~~~~~~~~
vim +533 init/initramfs.c
532
> 533 static bool __initdata initramfs_async = CONFIG_INITRAMFS_ASYNC;
534 static int __init initramfs_async_setup(char *str)
535 {
536 strtobool(str, &initramfs_async);
537 return 1;
538 }
539 __setup("initramfs_async=", initramfs_async_setup);
540
541 static __initdata struct work_struct initramfs_wrk;
542 static DECLARE_COMPLETION(initramfs_done);
543 static bool initramfs_unpack_started;
544
> 545 void _wait_for_initramfs(const char *caller)
546 {
547 unsigned long start;
548
549 if (try_wait_for_completion(&initramfs_done))
550 return;
551 if (!initramfs_unpack_started) {
552 /*
553 * Something before rootfs_initcall wants to access
554 * the filesystem/initramfs. Probably a bug. Make a
555 * note, avoid deadlocking the machine, and let the
556 * caller's access fail as it used to.
557 */
558 pr_warn_once("wait_for_initramfs() called by %s"
559 " before rootfs_initcalls\n", caller);
560 return;
561 }
562
563 start = jiffies;
564 wait_for_completion(&initramfs_done);
565 pr_info("%s() waited %lu jiffies for initramfs_done\n",
566 caller, jiffies - start);
567 }
568 EXPORT_SYMBOL_GPL(_wait_for_initramfs);
569
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 21739 bytes --]
next prev parent reply other threads:[~2021-02-24 22:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 14:29 [PATCH/RFC 0/2] background initramfs unpacking, and CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-02-24 14:29 ` [PATCH/RFC 1/2] init/initramfs.c: allow asynchronous unpacking Rasmus Villemoes
2021-02-24 17:17 ` Linus Torvalds
2021-02-24 22:13 ` Rasmus Villemoes
2021-02-24 17:58 ` kernel test robot
2021-02-24 21:37 ` kernel test robot
2021-02-24 22:09 ` kernel test robot [this message]
2021-03-02 16:26 ` Luis Chamberlain
2021-02-24 14:29 ` [PATCH/RFC 2/2] modules: add CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-02-24 22:19 ` [PATCH/RFC 0/2] background initramfs unpacking, and CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-03-09 21:16 ` [PATCH v2 " Rasmus Villemoes
2021-03-09 21:16 ` [PATCH v2 1/2] init/initramfs.c: allow asynchronous unpacking Rasmus Villemoes
2021-03-09 22:07 ` Linus Torvalds
2021-03-09 22:39 ` Rasmus Villemoes
2021-03-11 17:55 ` Luis Chamberlain
2021-03-11 17:55 ` Luis Chamberlain
2021-03-09 22:16 ` Linus Torvalds
2021-03-09 22:51 ` Rasmus Villemoes
2021-03-11 0:17 ` Rasmus Villemoes
2021-03-11 1:45 ` Rasmus Villemoes
2021-03-11 18:02 ` Linus Torvalds
2021-03-13 13:13 ` Rasmus Villemoes
2021-03-09 21:17 ` [PATCH v2 2/2] modules: add CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-03-10 9:46 ` Greg Kroah-Hartman
2021-03-11 13:28 ` Jessica Yu
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=202102250602.pN7AGbYf-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.