mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: WARNING: modpost: vmlinux.o(.text.unlikely+0x1998): Section mismatch in reference from the function trace_define_generic_fields.isra.0() to the variable .init.data:initcall_level_names
Date: Sun, 24 Jul 2022 19:26:01 -0400	[thread overview]
Message-ID: <20220724192601.5823c3af@rorschach.local.home> (raw)
In-Reply-To: <202207240538.J7vypIlv-lkp@intel.com>

On Sun, 24 Jul 2022 05:29:40 +0800
kernel test robot <lkp@intel.com> wrote:

> Hi Steven,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   515f71412bb73ebd7f41f90e1684fc80b8730789
> commit: a55f224ff5f238013de8762c4287117e47b86e22 tracing: Fix pid filtering when triggers are attached
> date:   8 months ago
> config: xtensa-randconfig-c023-20220722 (https://download.01.org/0day-ci/archive/20220724/202207240538.J7vypIlv-lkp@intel.com/config)
> compiler: xtensa-linux-gcc (GCC) 12.1.0

This is probably due to the xtensa compiler not inlining the function
like pretty much any other compiler does. It could use a __init, just
because the only function that calls this function also has an __init.

-- Steve


> 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/torvalds/linux.git/commit/?id=a55f224ff5f238013de8762c4287117e47b86e22
>         git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>         git fetch --no-tags linus master
>         git checkout a55f224ff5f238013de8762c4287117e47b86e22
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=xtensa SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
> 
> << WARNING: modpost: vmlinux.o(.text.unlikely+0x17c8): Section mismatch in reference from the function __trace_event_discard_commit() to the variable .init.data:initcall_level_names
> >> WARNING: modpost: vmlinux.o(.text.unlikely+0x1998): Section mismatch in reference from the function trace_define_generic_fields.isra.0() to the variable .init.data:initcall_level_names  
> The function trace_define_generic_fields.isra.0() references
> the variable __initdata initcall_level_names.
> This is often because trace_define_generic_fields.isra.0 lacks a __initdata
> annotation or the annotation of initcall_level_names is wrong.
> 


      reply	other threads:[~2022-07-24 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 21:29 kernel test robot
2022-07-24 23:26 ` Steven Rostedt [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=20220724192601.5823c3af@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    /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

all inboxes | Powered by JetHome®