All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.1 414/415] include/linux/jump_label.h:260:undefined reference to `__tracepoint_cros_security_socket_post_create_enter'
Date: Wed, 6 Nov 2024 18:17:09 +0800	[thread overview]
Message-ID: <202411061815.Cl75dvU4-lkp@intel.com> (raw)

tree:   https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.1
head:   eebfbf01bf6938dd13cb315873c55c135325ffe2
commit: 0c222baf9d509fdea61d5e821a175093d62f2f3b [414/415] CHROMIUM: add cros_security_post_create_exit tp
config: arm64-randconfig-001-20241106 (https://download.01.org/0day-ci/archive/20241106/202411061815.Cl75dvU4-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411061815.Cl75dvU4-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411061815.Cl75dvU4-lkp@intel.com/

All errors (new ones prefixed by >>):

   aarch64-linux-ld: Unexpected GOT/PLT entries detected!
   aarch64-linux-ld: Unexpected run-time procedure linkages detected!
   aarch64-linux-ld: ID map text too big or misaligned
   aarch64-linux-ld: security/security.o: in function `security_socket_post_create':
>> include/linux/jump_label.h:260:(.text+0xada4): undefined reference to `__tracepoint_cros_security_socket_post_create_enter'
   aarch64-linux-ld: security/security.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `__tracepoint_cros_security_socket_post_create_enter' which may bind externally can not be used when making a shared object; recompile with -fPIC
>> include/linux/jump_label.h:260:(.text+0xada4): dangerous relocation: unsupported relocation
>> aarch64-linux-ld: include/linux/jump_label.h:260:(.text+0xada8): undefined reference to `__tracepoint_cros_security_socket_post_create_enter'
   aarch64-linux-ld: security/security.o: in function `security_socket_post_create':
>> include/trace/events/cros_net.h:387:(.text+0xae3c): undefined reference to `__traceiter_cros_security_socket_post_create_enter'


vim +260 include/linux/jump_label.h

1f69bf9c613760 Jason Baron    2016-08-03  257  
656d054e0a15ec Peter Zijlstra 2022-05-02  258  static __always_inline int static_key_count(struct static_key *key)
4c5ea0a9cd02d6 Paolo Bonzini  2016-06-21  259  {
656d054e0a15ec Peter Zijlstra 2022-05-02 @260  	return arch_atomic_read(&key->enabled);
4c5ea0a9cd02d6 Paolo Bonzini  2016-06-21  261  }
4c5ea0a9cd02d6 Paolo Bonzini  2016-06-21  262  

:::::: The code at line 260 was first introduced by commit
:::::: 656d054e0a15ec327bd82801ccd58201e59f6896 jump_label,noinstr: Avoid instrumentation for JUMP_LABEL=n builds

:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Peter Zijlstra <peterz@infradead.org>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-11-06 10:17 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=202411061815.Cl75dvU4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.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.