All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ardb:arm32-ftrace-fixes 41/50] WARNING: modpost: vmlinux.o(.text+0x3aec0): Section mismatch in reference from the function ftrace_make_call() to the function .init.text:ftrace_caller_from_init()
Date: Thu, 27 Jan 2022 10:42:57 +0800	[thread overview]
Message-ID: <202201271012.knG6huUI-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3791 bytes --]

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git arm32-ftrace-fixes
head:   db81a4be9a228c6d728b5e10ada88553cc72a001
commit: 3266348765f2d19ca7605c25f50ee04fd4a5decf [41/50] ARM: ftrace: use trampolines to keep .init.text in branching range
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20220127/202201271012.knG6huUI-lkp(a)intel.com/config)
compiler: arm-linux-gnueabi-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/ardb/linux.git/commit/?id=3266348765f2d19ca7605c25f50ee04fd4a5decf
        git remote add ardb git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git
        git fetch --no-tags ardb arm32-ftrace-fixes
        git checkout 3266348765f2d19ca7605c25f50ee04fd4a5decf
        # 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=arm 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+0x3aec0): Section mismatch in reference from the function ftrace_make_call() to the function .init.text:ftrace_caller_from_init()
The function ftrace_make_call() references
the function __init ftrace_caller_from_init().
This is often because ftrace_make_call lacks a __init
annotation or the annotation of ftrace_caller_from_init is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x3aec4): Section mismatch in reference from the function ftrace_make_call() to the function .init.text:ftrace_regs_caller_from_init()
The function ftrace_make_call() references
the function __init ftrace_regs_caller_from_init().
This is often because ftrace_make_call lacks a __init
annotation or the annotation of ftrace_regs_caller_from_init is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x3b178): Section mismatch in reference from the function ftrace_modify_call() to the function .init.text:ftrace_caller_from_init()
The function ftrace_modify_call() references
the function __init ftrace_caller_from_init().
This is often because ftrace_modify_call lacks a __init
annotation or the annotation of ftrace_caller_from_init is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x3b17c): Section mismatch in reference from the function ftrace_modify_call() to the function .init.text:ftrace_regs_caller_from_init()
The function ftrace_modify_call() references
the function __init ftrace_regs_caller_from_init().
This is often because ftrace_modify_call lacks a __init
annotation or the annotation of ftrace_regs_caller_from_init is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x3b484): Section mismatch in reference from the function ftrace_make_nop() to the function .init.text:ftrace_caller_from_init()
The function ftrace_make_nop() references
the function __init ftrace_caller_from_init().
This is often because ftrace_make_nop lacks a __init
annotation or the annotation of ftrace_caller_from_init is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x3b488): Section mismatch in reference from the function ftrace_make_nop() to the function .init.text:ftrace_regs_caller_from_init()
The function ftrace_make_nop() references
the function __init ftrace_regs_caller_from_init().
This is often because ftrace_make_nop lacks a __init
annotation or the annotation of ftrace_regs_caller_from_init is wrong.

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

                 reply	other threads:[~2022-01-27  2:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202201271012.knG6huUI-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.