From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: net-procfs.c:(.ref.text+0x60): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `wext_proc_exit'
Date: Mon, 5 Feb 2024 13:07:49 +0800 [thread overview]
Message-ID: <202402051349.XPu1hxff-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only kconfig file changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Mark Salyzyn <salyzyn@google.com>
tree: https://github.com/ambarus/linux-0day syzkaller-id-5ecbc557fcdb8a2864e876f690ef377db999c50f
head: caa714448992ba4eb583735a4acb26917fbc67a8
commit: 8a167346a33aa28c6e422739e69abc87f57f81bc ANDROID: net: enable wireless core features with GKI_LEGACY_WEXT_ALLCONFIG
date: 4 years, 5 months ago
:::::: branch date: 1 year, 2 months ago
:::::: commit date: 4 years, 5 months ago
config: arm64-randconfig-001-20240117 (https://download.01.org/0day-ci/archive/20240205/202402051349.XPu1hxff-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240205/202402051349.XPu1hxff-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/r/202402051349.XPu1hxff-lkp@intel.com/
Note: the ambarus/syzkaller-id-5ecbc557fcdb8a2864e876f690ef377db999c50f HEAD caa714448992ba4eb583735a4acb26917fbc67a8 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
aarch64-linux-ld: warning: .tmp_vmlinux1 has a LOAD segment with RWX permissions
aarch64-linux-ld: net/socket.o: in function `sock_ioctl':
socket.c:(.text+0x32cc): undefined reference to `wext_handle_ioctl'
socket.c:(.text+0x32cc): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `wext_handle_ioctl'
aarch64-linux-ld: net/socket.o: in function `compat_sock_ioctl':
socket.c:(.text+0x497c): undefined reference to `compat_wext_handle_ioctl'
socket.c:(.text+0x497c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `compat_wext_handle_ioctl'
aarch64-linux-ld: net/core/net-procfs.o: in function `dev_proc_net_exit':
net-procfs.c:(.ref.text+0x60): undefined reference to `wext_proc_exit'
>> net-procfs.c:(.ref.text+0x60): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `wext_proc_exit'
aarch64-linux-ld: net/core/net-procfs.o: in function `dev_proc_net_init':
net-procfs.c:(.init.text+0x100): undefined reference to `wext_proc_init'
>> net-procfs.c:(.init.text+0x100): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `wext_proc_init'
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for WIRELESS_EXT
Depends on [n]: NET [=y] && WIRELESS [=n]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_CORE
Depends on [n]: NET [=y] && WIRELESS [=n] && (CFG80211_WEXT [=n] || WIRELESS_EXT [=y])
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_PROC
Depends on [n]: NET [=y] && WIRELESS [=n] && PROC_FS [=y] && WEXT_CORE [=y]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_PRIV
Depends on [n]: NET [=y] && WIRELESS [=n]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_SPY
Depends on [n]: NET [=y] && WIRELESS [=n]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-02-05 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 5:07 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 9:32 net-procfs.c:(.ref.text+0x60): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `wext_proc_exit' 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=202402051349.XPu1hxff-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.