From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Kurt Kanzenbach <kurt@linutronix.de>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [tip:timers/core 1/8] WARNING: modpost: vmlinux.o(.text+0xc28c04): Section mismatch in reference from the function sock_from_file() to the variable .init.text:.LFB3599
Date: Mon, 9 May 2022 21:59:23 +0800 [thread overview]
Message-ID: <YnkeO+9cLB+Ydsun@rli9-dbox> (raw)
In-Reply-To: <202205091925.kRfA1mR4-lkp@intel.com>
On Mon, May 09, 2022 at 07:26:29PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/core
> head: f4b62e1e1137507268c2c63dc4e6da279dc58e9f
> commit: 3dc6ffae2da201284cb24af66af77ee0bbb2efaa [1/8] timekeeping: Introduce fast accessor to clock tai
> config: riscv-randconfig-r042-20220509 (https://download.01.org/0day-ci/archive/20220509/202205091925.kRfA1mR4-lkp@intel.com/config)
> compiler: riscv32-linux-gcc (GCC) 11.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://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=3dc6ffae2da201284cb24af66af77ee0bbb2efaa
> git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> git fetch --no-tags tip timers/core
> git checkout 3dc6ffae2da201284cb24af66af77ee0bbb2efaa
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=riscv 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 <<):
Sorry, kindly ignore this report, which is a false positive. We will
block such report in future.
>
> >> WARNING: modpost: vmlinux.o(.text+0xc28c04): Section mismatch in reference from the function sock_from_file() to the variable .init.text:.LFB3599
> The function sock_from_file() references
> the variable __init .LFB3599.
> This is often because sock_from_file lacks a __init
> annotation or the annotation of .LFB3599 is wrong.
>
> Note: the below error/warnings can be found in parent commit:
> << WARNING: modpost: vmlinux.o(.text+0xbad7d2): Section mismatch in reference from the function comedi_proc_cleanup() to the variable .init.text:.L0
> << WARNING: modpost: vmlinux.o(.exit.text+0x8562): Section mismatch in reference from the function lirc_dev_exit() to the variable .init.text:.L0
> << WARNING: modpost: vmlinux.o(__ex_table+0x141c): Section mismatch in reference from the variable .L0 to the variable .debug_rnglists:.LLRL39
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
prev parent reply other threads:[~2022-05-09 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 11:26 [tip:timers/core 1/8] WARNING: modpost: vmlinux.o(.text+0xc28c04): Section mismatch in reference from the function sock_from_file() to the variable .init.text:.LFB3599 kernel test robot
2022-05-09 13:59 ` Philip Li [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=YnkeO+9cLB+Ydsun@rli9-dbox \
--to=philip.li@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox