From: kernel test robot <[email protected]>
To: Peter Zijlstra <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
[email protected],
Thomas Gleixner <[email protected]>
Subject: [ammarfaizi2-block:tglx/devel/depthtracking 33/59] vmlinux.o: warning: objtool: __asan_load1+0x4e: return with UACCESS disabled from a UACCESS-safe function
Date: Tue, 16 Aug 2022 10:27:22 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block tglx/devel/depthtracking
head: 9bbf33b92f4c755dd56f4d9bc1b40e94fdd1fff7
commit: c5803edfd11acd1bb56cd1878381c0c8b0902828 [33/59] objtool: Fix find_{symbol,func}_containing()
config: x86_64-randconfig-c002-20220815 (https://download.01.org/0day-ci/archive/20220816/[email protected]/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/c5803edfd11acd1bb56cd1878381c0c8b0902828
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block tglx/devel/depthtracking
git checkout c5803edfd11acd1bb56cd1878381c0c8b0902828
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: __asan_load1+0x4e: return with UACCESS disabled from a UACCESS-safe function
vmlinux.o: warning: objtool: __asan_store1_noabort+0x51: return with UACCESS enabled
vmlinux.o: warning: objtool: __asan_load2+0x74: return with UACCESS disabled from a UACCESS-safe function
vmlinux.o: warning: objtool: __asan_store2_noabort+0x77: return with UACCESS enabled
vmlinux.o: warning: objtool: __asan_load4_noabort+0x73: return with UACCESS enabled
vmlinux.o: warning: objtool: __asan_store4_noabort+0x76: return with UACCESS enabled
vmlinux.o: warning: objtool: __asan_load8_noabort+0x7c: return with UACCESS enabled
vmlinux.o: warning: objtool: __asan_store8_noabort+0x7f: return with UACCESS enabled
vmlinux.o: warning: objtool: __asan_load16+0x6d: return with UACCESS disabled from a UACCESS-safe function
vmlinux.o: warning: objtool: __asan_store16+0x70: return with UACCESS disabled from a UACCESS-safe function
>> vmlinux.o: warning: objtool: __asan_loadN+0x14: return with UACCESS disabled from a UACCESS-safe function
vmlinux.o: warning: objtool: __asan_storeN_noabort+0x17: return with UACCESS enabled
objdump-func vmlinux.o __asan_load1:
0000 00000000004af802 <__asan_load1>:
0000 4af802: f3 0f 1e fa endbr64
0004 4af806: 55 push %rbp
0005 4af807: 48 89 e5 mov %rsp,%rbp
0008 4af80a: 48 8b 4d 08 mov 0x8(%rbp),%rcx
000c 4af80e: 48 83 ff ff cmp $0xffffffffffffffff,%rdi
0010 4af812: 74 2f je 4af843 <__asan_load1+0x41>
0012 4af814: 48 b8 ff ff ff ff ff 7f ff ff movabs $0xffff7fffffffffff,%rax
001c 4af81e: 48 39 c7 cmp %rax,%rdi
001f 4af821: 76 20 jbe 4af843 <__asan_load1+0x41>
0021 4af823: 48 89 fa mov %rdi,%rdx
0024 4af826: b8 ff ff 37 00 mov $0x37ffff,%eax
0029 4af82b: 48 c1 ea 03 shr $0x3,%rdx
002d 4af82f: 48 c1 e0 2a shl $0x2a,%rax
0031 4af833: 8a 04 02 mov (%rdx,%rax,1),%al
0034 4af836: 84 c0 test %al,%al
0036 4af838: 74 15 je 4af84f <__asan_load1+0x4d>
0038 4af83a: 89 fa mov %edi,%edx
003a 4af83c: 83 e2 07 and $0x7,%edx
003d 4af83f: 38 d0 cmp %dl,%al
003f 4af841: 7f 0c jg 4af84f <__asan_load1+0x4d>
0041 4af843: 31 d2 xor %edx,%edx
0043 4af845: be 01 00 00 00 mov $0x1,%esi
0048 4af84a: e8 00 00 00 00 call 4af84f <__asan_load1+0x4d> 4af84b: R_X86_64_PLT32 kasan_report-0x4
004d 4af84f: 5d pop %rbp
004e 4af850: c3 ret
004f 4af851: cc int3
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-16 2:27 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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