From: "Chen, Rong A" <[email protected]>
To: Peter Zijlstra <[email protected]>, kernel test robot <[email protected]>
Cc: [email protected],
GNU/Weeb Mailing List <[email protected]>,
[email protected], Sasha Levin <[email protected]>,
Borislav Petkov <[email protected]>
Subject: Re: [kbuild-all] Re: [ammarfaizi2-block:stable/linux-stable-rc/queue/5.15 146/150] kernel/futex.o: warning: objtool: futex_atomic_op_inuser()+0xb8: unreachable instruction
Date: Thu, 12 May 2022 17:30:20 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/12/2022 4:17 PM, Peter Zijlstra wrote:
> On Thu, May 12, 2022 at 10:00:33AM +0800, kernel test robot wrote:
>> tree: https://github.com/ammarfaizi2/linux-block stable/linux-stable-rc/queue/5.15
>> head: 305e905f70311e1b49cc730931a19c3e364f4d8c
>> commit: 45dc9d706619a6814e4063d5431483f94badb5a1 [146/150] x86: Add straight-line-speculation mitigation
>> config: x86_64-randconfig-m001-20220509 (https://download.01.org/0day-ci/archive/20220512/[email protected]/config)
>> compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
>> reproduce (this is a W=1 build):
>> # https://github.com/ammarfaizi2/linux-block/commit/45dc9d706619a6814e4063d5431483f94badb5a1
>> git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
>> git fetch --no-tags ammarfaizi2-block stable/linux-stable-rc/queue/5.15
>> git checkout 45dc9d706619a6814e4063d5431483f94badb5a1
>> # 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 as appropriate
>> Reported-by: kernel test robot <[email protected]>
>>
>> All warnings (new ones prefixed by >>):
>>
>>>> kernel/futex.o: warning: objtool: futex_atomic_op_inuser()+0xb8: unreachable instruction
>> --
>>>> mm/madvise.o: warning: objtool: madvise_behavior()+0x69: unreachable instruction
>> --
>>>> kernel/bpf/btf.o: warning: objtool: __btf_resolve_size()+0x72: unreachable instruction
>
> Would it be possible for the robot to include the output of this script:
Hi Peter,
Thanks for your advice, we'll support it asap.
Best Regards,
Rong Chen
>
> https://lkml.kernel.org/r/3eb3f091fd6bd9caba50392ceab98ce756804f3b.1650578171.git.jpoimboe@redhat.com
>
> for each objtool warning it gives (as run on vmlinux.o):
>
> $ ./scripts/objdump-func build-output/vmlinux.o futex_atomic_op_inuser
> $ ./scripts/objdump-func build-output/vmlinux.o madvise_behavior
> $ ./scripts/objdump-func build-output/vmlinux.o __btf_resolve_size
>
> etc.. that would make it easier to see what the problem is without
> having to reproduce the build.
>
> A super wild guess; but try this commit:
>
> 1ffbe4e935f9 ("objtool: Default ignore INT3 for unreachable")
>
> _______________________________________________
> kbuild-all mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
next prev parent reply other threads:[~2022-05-12 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 2:00 [ammarfaizi2-block:stable/linux-stable-rc/queue/5.15 146/150] kernel/futex.o: warning: objtool: futex_atomic_op_inuser()+0xb8: unreachable instruction kernel test robot
2022-05-12 8:17 ` Peter Zijlstra
2022-05-12 9:30 ` Chen, Rong A [this message]
2022-05-12 17:11 ` Josh Poimboeuf
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] \
[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