From: Rong Chen <rong.a.chen@intel.com>
To: Frederic Weisbecker <frederic@kernel.org>,
kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [kbuild-all] Re: arch/x86/mm/fault.o: warning: objtool: do_page_fault()+0x4fb: unreachable instruction
Date: Mon, 9 Mar 2020 16:37:24 +0800 [thread overview]
Message-ID: <d242f3cb-e95b-441e-0a32-a0279100eeaf@intel.com> (raw)
In-Reply-To: <20200306142732.GA8590@lenoir>
On 3/6/20 10:27 PM, Frederic Weisbecker wrote:
> On Fri, Mar 06, 2020 at 06:48:47PM +0800, kbuild test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 9f65ed5fe41ce08ed1cb1f6a950f9ec694c142ad
>> commit: ee6352b2c47a24234398e06381edd93a8e965976 x86/context-tracking: Remove exception_enter/exit() from do_page_fault()
>> date: 8 weeks ago
>> config: x86_64-randconfig-a002-20200306 (attached as .config)
>> compiler: gcc-4.9 (Debian 4.9.2-10+deb8u1) 4.9.2
>> reproduce:
>> git checkout ee6352b2c47a24234398e06381edd93a8e965976
>> # save the attached .config to linux build tree
>> make ARCH=x86_64
>>
>> If you fix the issue, kindly add following tag
>> Reported-by: kbuild test robot <lkp@intel.com>
>>
>> All warnings (new ones prefixed by >>):
>>
>>>> arch/x86/mm/fault.o: warning: objtool: do_page_fault()+0x4fb: unreachable instruction
> I tried several versions of gcc and I can't reproduce the warning. Also looking
> at the code I fail to find an actual unreachable path. Do you still have the vmlinux around?
>
>
Hi Frederic,
Sorry for the inconvenience, we checked again and only found this issue
on gcc-4.9.2,
and there's no issue on gcc-4.9.3 or other new versions.
Best Regards,
Rong Chen
prev parent reply other threads:[~2020-03-09 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 10:48 arch/x86/mm/fault.o: warning: objtool: do_page_fault()+0x4fb: unreachable instruction kbuild test robot
2020-03-06 14:27 ` Frederic Weisbecker
2020-03-09 8:37 ` Rong Chen [this message]
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=d242f3cb-e95b-441e-0a32-a0279100eeaf@intel.com \
--to=rong.a.chen@intel.com \
--cc=frederic@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
/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