* [linux-next:master 3136/3150] init/main.c:925:2: error: implicit declaration of function 'init_vmlinux_build_id'
@ 2021-05-15 20:25 kernel test robot
2021-05-15 21:15 ` Stephen Boyd
0 siblings, 1 reply; 2+ messages in thread
From: kernel test robot @ 2021-05-15 20:25 UTC (permalink / raw)
To: Stephen Boyd; +Cc: kbuild-all, Linux Memory Management List, Andrew Morton
[-- Attachment #1: Type: text/plain, Size: 6857 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: cd557f1c605fc5a2c0eb0b540610f50dc67dd849
commit: 9bbb6ec7e7a5cbc59222379498d5a3b8ac21080a [3136/3150] buildid: stash away kernels build ID on init
config: x86_64-randconfig-a005-20210514 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9bbb6ec7e7a5cbc59222379498d5a3b8ac21080a
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 9bbb6ec7e7a5cbc59222379498d5a3b8ac21080a
# save the attached .config to linux build tree
make W=1 W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Note: the linux-next/master HEAD cd557f1c605fc5a2c0eb0b540610f50dc67dd849 builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
init/main.c: In function 'start_kernel':
>> init/main.c:925:2: error: implicit declaration of function 'init_vmlinux_build_id' [-Werror=implicit-function-declaration]
925 | init_vmlinux_build_id();
| ^~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/init_vmlinux_build_id +925 init/main.c
916
917 asmlinkage __visible void __init __no_sanitize_address start_kernel(void)
918 {
919 char *command_line;
920 char *after_dashes;
921
922 set_task_stack_end_magic(&init_task);
923 smp_setup_processor_id();
924 debug_objects_early_init();
> 925 init_vmlinux_build_id();
926
927 cgroup_init_early();
928
929 local_irq_disable();
930 early_boot_irqs_disabled = true;
931
932 /*
933 * Interrupts are still disabled. Do necessary setups, then
934 * enable them.
935 */
936 boot_cpu_init();
937 page_address_init();
938 pr_notice("%s", linux_banner);
939 early_security_init();
940 setup_arch(&command_line);
941 setup_boot_config();
942 setup_command_line(command_line);
943 setup_nr_cpu_ids();
944 setup_per_cpu_areas();
945 smp_prepare_boot_cpu(); /* arch-specific boot-cpu hooks */
946 boot_cpu_hotplug_init();
947
948 build_all_zonelists(NULL);
949 page_alloc_init();
950
951 pr_notice("Kernel command line: %s\n", saved_command_line);
952 /* parameters may set static keys */
953 jump_label_init();
954 parse_early_param();
955 after_dashes = parse_args("Booting kernel",
956 static_command_line, __start___param,
957 __stop___param - __start___param,
958 -1, -1, NULL, &unknown_bootoption);
959 print_unknown_bootoptions();
960 if (!IS_ERR_OR_NULL(after_dashes))
961 parse_args("Setting init args", after_dashes, NULL, 0, -1, -1,
962 NULL, set_init_arg);
963 if (extra_init_args)
964 parse_args("Setting extra init args", extra_init_args,
965 NULL, 0, -1, -1, NULL, set_init_arg);
966
967 /*
968 * These use large bootmem allocations and must precede
969 * kmem_cache_init()
970 */
971 setup_log_buf(0);
972 vfs_caches_init_early();
973 sort_main_extable();
974 trap_init();
975 mm_init();
976
977 ftrace_init();
978
979 /* trace_printk can be enabled here */
980 early_trace_init();
981
982 /*
983 * Set up the scheduler prior starting any interrupts (such as the
984 * timer interrupt). Full topology setup happens at smp_init()
985 * time - but meanwhile we still have a functioning scheduler.
986 */
987 sched_init();
988
989 if (WARN(!irqs_disabled(),
990 "Interrupts were enabled *very* early, fixing it\n"))
991 local_irq_disable();
992 radix_tree_init();
993
994 /*
995 * Set up housekeeping before setting up workqueues to allow the unbound
996 * workqueue to take non-housekeeping into account.
997 */
998 housekeeping_init();
999
1000 /*
1001 * Allow workqueue creation and work item queueing/cancelling
1002 * early. Work item execution depends on kthreads and starts after
1003 * workqueue_init().
1004 */
1005 workqueue_init_early();
1006
1007 rcu_init();
1008
1009 /* Trace events are available after this */
1010 trace_init();
1011
1012 if (initcall_debug)
1013 initcall_debug_enable();
1014
1015 context_tracking_init();
1016 /* init some links before init_ISA_irqs() */
1017 early_irq_init();
1018 init_IRQ();
1019 tick_init();
1020 rcu_init_nohz();
1021 init_timers();
1022 srcu_init();
1023 hrtimers_init();
1024 softirq_init();
1025 timekeeping_init();
1026 kfence_init();
1027
1028 /*
1029 * For best initial stack canary entropy, prepare it after:
1030 * - setup_arch() for any UEFI RNG entropy and boot cmdline access
1031 * - timekeeping_init() for ktime entropy used in rand_initialize()
1032 * - rand_initialize() to get any arch-specific entropy like RDRAND
1033 * - add_latent_entropy() to get any latent entropy
1034 * - adding command line entropy
1035 */
1036 rand_initialize();
1037 add_latent_entropy();
1038 add_device_randomness(command_line, strlen(command_line));
1039 boot_init_stack_canary();
1040
1041 time_init();
1042 perf_event_init();
1043 profile_init();
1044 call_function_init();
1045 WARN(!irqs_disabled(), "Interrupts were enabled early\n");
1046
1047 early_boot_irqs_disabled = false;
1048 local_irq_enable();
1049
1050 kmem_cache_init_late();
1051
1052 /*
1053 * HACK ALERT! This is early. We're enabling the console before
1054 * we've done PCI setups etc, and console_init() must be aware of
1055 * this. But we do want output early, in case something goes wrong.
1056 */
1057 console_init();
1058 if (panic_later)
1059 panic("Too many boot %s vars at `%s'", panic_later,
1060 panic_param);
1061
1062 lockdep_init();
1063
1064 /*
1065 * Need to run this when irqs are enabled, because it wants
1066 * to self-test [hard/soft]-irqs on/off lock inversion bugs
1067 * too:
1068 */
1069 locking_selftest();
1070
1071 /*
1072 * This needs to be called before any devices perform DMA
1073 * operations that might use the SWIOTLB bounce buffers. It will
1074 * mark the bounce buffers as decrypted so that their usage will
1075 * not cause "plain-text" data to be decrypted when accessed.
1076 */
1077 mem_encrypt_init();
1078
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33682 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-next:master 3136/3150] init/main.c:925:2: error: implicit declaration of function 'init_vmlinux_build_id'
2021-05-15 20:25 [linux-next:master 3136/3150] init/main.c:925:2: error: implicit declaration of function 'init_vmlinux_build_id' kernel test robot
@ 2021-05-15 21:15 ` Stephen Boyd
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Boyd @ 2021-05-15 21:15 UTC (permalink / raw)
To: kernel test robot; +Cc: kbuild-all, Linux Memory Management List, Andrew Morton
Quoting kernel test robot (2021-05-15 13:25:22)
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: cd557f1c605fc5a2c0eb0b540610f50dc67dd849
> commit: 9bbb6ec7e7a5cbc59222379498d5a3b8ac21080a [3136/3150] buildid: stash away kernels build ID on init
> config: x86_64-randconfig-a005-20210514 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9bbb6ec7e7a5cbc59222379498d5a3b8ac21080a
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 9bbb6ec7e7a5cbc59222379498d5a3b8ac21080a
> # save the attached .config to linux build tree
> make W=1 W=1 ARCH=x86_64
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> Note: the linux-next/master HEAD cd557f1c605fc5a2c0eb0b540610f50dc67dd849 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> init/main.c: In function 'start_kernel':
> >> init/main.c:925:2: error: implicit declaration of function 'init_vmlinux_build_id' [-Werror=implicit-function-declaration]
> 925 | init_vmlinux_build_id();
> | ^~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
Thanks. This patch should fix it. Andrew, can it be squashed in?
diff --git a/init/main.c b/init/main.c
index eaede2f41327..38982b688431 100644
--- a/init/main.c
+++ b/init/main.c
@@ -44,6 +44,7 @@
#include <linux/rcupdate.h>
#include <linux/moduleparam.h>
#include <linux/kallsyms.h>
+#include <linux/buildid.h>
#include <linux/writeback.h>
#include <linux/cpu.h>
#include <linux/cpuset.h>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-05-15 21:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-15 20:25 [linux-next:master 3136/3150] init/main.c:925:2: error: implicit declaration of function 'init_vmlinux_build_id' kernel test robot
2021-05-15 21:15 ` Stephen Boyd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox