From: dust.li <dust.li@linux.alibaba.com>
To: kbuild-all@lists.01.org
Subject: Re: [saeed:net-next-mlx5 100/108] WARNING: modpost: vmlinux.o(.text+0x1fc2f20): Section mismatch in reference from the function trace_event_raw_event_smc_msg_event() to the variable .init.data:initcall_level_names
Date: Wed, 02 Mar 2022 11:12:47 +0800 [thread overview]
Message-ID: <20220302031247.GC9417@linux.alibaba.com> (raw)
In-Reply-To: <202203020919.C37R7nSW-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
On Wed, Mar 02, 2022 at 10:51:58AM +0800, kernel test robot wrote:
>tree: https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git net-next-mlx5
>head: f6aab83b7decaf651cffe7fdac7d0bb316ea6bca
>commit: 462791bbfa350189e309a5a94541f6b63cd874e8 [100/108] net/smc: add sysctl interface for SMC
>config: xtensa-randconfig-r034-20220301 (https://download.01.org/0day-ci/archive/20220302/202203020919.C37R7nSW-lkp(a)intel.com/config)
>compiler: xtensa-linux-gcc (GCC) 11.2.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://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/commit/?id=462791bbfa350189e309a5a94541f6b63cd874e8
> git remote add saeed https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
> git fetch --no-tags saeed net-next-mlx5
> git checkout 462791bbfa350189e309a5a94541f6b63cd874e8
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=xtensa SHELL=/bin/bash
>
>If you fix the issue, kindly add following tag as appropriate
>Reported-by: kernel test robot <lkp@intel.com>
>
>All warnings (new ones prefixed by >>, old ones prefixed by <<):
>
>>> WARNING: modpost: vmlinux.o(.text+0x1fc2f20): Section mismatch in reference from the function trace_event_raw_event_smc_msg_event() to the variable .init.data:initcall_level_names
>The function trace_event_raw_event_smc_msg_event() references
>the variable __initdata initcall_level_names.
>This is often because trace_event_raw_event_smc_msg_event lacks a __initdata
>annotation or the annotation of initcall_level_names is wrong.
Really sorry for the break !
I think its because we missed the '__net_exit' annotation for
smc_sysctl_exit(). I will send a patch to fix this soon
>
>---
>0-DAY CI Kernel Test Service, Intel Corporation
>https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: "dust.li" <dust.li@linux.alibaba.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Tony Lu <tonylu@linux.alibaba.com>
Subject: Re: [saeed:net-next-mlx5 100/108] WARNING: modpost: vmlinux.o(.text+0x1fc2f20): Section mismatch in reference from the function trace_event_raw_event_smc_msg_event() to the variable .init.data:initcall_level_names
Date: Wed, 2 Mar 2022 11:12:47 +0800 [thread overview]
Message-ID: <20220302031247.GC9417@linux.alibaba.com> (raw)
In-Reply-To: <202203020919.C37R7nSW-lkp@intel.com>
On Wed, Mar 02, 2022 at 10:51:58AM +0800, kernel test robot wrote:
>tree: https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git net-next-mlx5
>head: f6aab83b7decaf651cffe7fdac7d0bb316ea6bca
>commit: 462791bbfa350189e309a5a94541f6b63cd874e8 [100/108] net/smc: add sysctl interface for SMC
>config: xtensa-randconfig-r034-20220301 (https://download.01.org/0day-ci/archive/20220302/202203020919.C37R7nSW-lkp@intel.com/config)
>compiler: xtensa-linux-gcc (GCC) 11.2.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://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/commit/?id=462791bbfa350189e309a5a94541f6b63cd874e8
> git remote add saeed https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git
> git fetch --no-tags saeed net-next-mlx5
> git checkout 462791bbfa350189e309a5a94541f6b63cd874e8
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=xtensa SHELL=/bin/bash
>
>If you fix the issue, kindly add following tag as appropriate
>Reported-by: kernel test robot <lkp@intel.com>
>
>All warnings (new ones prefixed by >>, old ones prefixed by <<):
>
>>> WARNING: modpost: vmlinux.o(.text+0x1fc2f20): Section mismatch in reference from the function trace_event_raw_event_smc_msg_event() to the variable .init.data:initcall_level_names
>The function trace_event_raw_event_smc_msg_event() references
>the variable __initdata initcall_level_names.
>This is often because trace_event_raw_event_smc_msg_event lacks a __initdata
>annotation or the annotation of initcall_level_names is wrong.
Really sorry for the break !
I think its because we missed the '__net_exit' annotation for
smc_sysctl_exit(). I will send a patch to fix this soon
>
>---
>0-DAY CI Kernel Test Service, Intel Corporation
>https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-03-02 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 2:51 [saeed:net-next-mlx5 100/108] WARNING: modpost: vmlinux.o(.text+0x1fc2f20): Section mismatch in reference from the function trace_event_raw_event_smc_msg_event() to the variable .init.data:initcall_level_names kernel test robot
2022-03-02 3:12 ` dust.li [this message]
2022-03-02 3:12 ` dust.li
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=20220302031247.GC9417@linux.alibaba.com \
--to=dust.li@linux.alibaba.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.