From: kernel test robot <lkp@intel.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mark:arm64/module-space-rework 6/7] arch/arm64/kernel/ftrace.c:200:36: error: invalid use of undefined type 'struct module'
Date: Mon, 8 May 2023 11:03:24 +0800 [thread overview]
Message-ID: <202305081035.i0vMAOOz-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm64/module-space-rework
head: a96e2e587515d06f8caeb9a27c144f7d33b93d20
commit: cc163cbb102f4856e1e1b3a87b530f223cd509ff [6/7] arm64: module: mandate MODULE_PLTS
config: arm64-randconfig-c041-20230507 (https://download.01.org/0day-ci/archive/20230508/202305081035.i0vMAOOz-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.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/mark/linux.git/commit/?id=cc163cbb102f4856e1e1b3a87b530f223cd509ff
git remote add mark https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git
git fetch --no-tags mark arm64/module-space-rework
git checkout cc163cbb102f4856e1e1b3a87b530f223cd509ff
# 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=arm64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/kernel/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202305081035.i0vMAOOz-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/arm64/kernel/ftrace.c: In function 'get_ftrace_plt':
>> arch/arm64/kernel/ftrace.c:200:36: error: invalid use of undefined type 'struct module'
200 | struct plt_entry *plt = mod->arch.ftrace_trampolines;
| ^~
vim +200 arch/arm64/kernel/ftrace.c
bd7d38dbdf356e AKASHI Takahiro 2014-04-30 197
3b23e4991fb66f Torsten Duwe 2019-02-08 198 static struct plt_entry *get_ftrace_plt(struct module *mod, unsigned long addr)
3b23e4991fb66f Torsten Duwe 2019-02-08 199 {
3b23e4991fb66f Torsten Duwe 2019-02-08 @200 struct plt_entry *plt = mod->arch.ftrace_trampolines;
3b23e4991fb66f Torsten Duwe 2019-02-08 201
3b23e4991fb66f Torsten Duwe 2019-02-08 202 if (addr == FTRACE_ADDR)
3b23e4991fb66f Torsten Duwe 2019-02-08 203 return &plt[FTRACE_PLT_IDX];
cc163cbb102f48 Mark Rutland 2023-04-19 204
3b23e4991fb66f Torsten Duwe 2019-02-08 205 return NULL;
3b23e4991fb66f Torsten Duwe 2019-02-08 206 }
3b23e4991fb66f Torsten Duwe 2019-02-08 207
:::::: The code at line 200 was first introduced by commit
:::::: 3b23e4991fb66f6d152f9055ede271a726ef9f21 arm64: implement ftrace with regs
:::::: TO: Torsten Duwe <duwe@lst.de>
:::::: CC: Mark Rutland <mark.rutland@arm.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-05-08 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 3:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-22 1:33 [mark:arm64/module-space-rework 6/7] arch/arm64/kernel/ftrace.c:200:36: error: invalid use of undefined type 'struct module' kernel test robot
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=202305081035.i0vMAOOz-lkp@intel.com \
--to=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.