From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Nov 15 (objtool)
Date: Mon, 20 Jan 2020 09:37:43 -0600 [thread overview]
Message-ID: <20200120153743.z6ws3jbgnsmsjvvx@treble> (raw)
In-Reply-To: <20191115163830.g262y75w3sh535fm@treble>
On Fri, Nov 15, 2019 at 10:38:30AM -0600, Josh Poimboeuf wrote:
> On Fri, Nov 15, 2019 at 08:02:30AM -0800, Randy Dunlap wrote:
> > On 11/15/19 12:05 AM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20191114:
> > >
> >
> > on x86_64:
> >
> > already reported and Josh supplied a fix (yet unmerged),
> > but this is still around:
> >
> > kernel/exit.o: warning: objtool: __x64_sys_exit_group()+0x14: unreachable instruction
>
> My apologies, I have a growing backlog of objtool fixes which I hope to
> post next week.
>
> >
> > new AFAIK:
> >
> > drivers/gpu/drm/bridge/cdns-dsi.o: warning: objtool: cdns_dsi_bridge_enable()+0x3e0: unreachable instruction
> >
> > obj file for latter one is attached.
>
> This seems fishy. cdns_dsi_init_link() never returns, it always dies a
> with UD2. I bet GCC decided that it always does a divide-by-zero, and
> so it forces a crash as a result. Will try to dig deeper next week...
Hi Randy,
(Digging up old objtool threads...)
This is another one that it would be nice to recreate, so I can open a
GCC bug if needed. If you can still recreate it, can you provide the
config file and GCC version?
--
Josh
next prev parent reply other threads:[~2020-01-20 15:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 8:05 linux-next: Tree for Nov 15 Stephen Rothwell
2019-11-15 16:02 ` linux-next: Tree for Nov 15 (objtool) Randy Dunlap
2019-11-15 16:38 ` Josh Poimboeuf
2020-01-20 15:37 ` Josh Poimboeuf [this message]
2019-11-15 16:11 ` linux-next: Tree for Nov 15 Naresh Kamboju
2019-11-15 16:17 ` linux-next: Tree for Nov 15 (drivers/md/dm-integrity) Randy Dunlap
2019-11-15 16:19 ` Randy Dunlap
2019-11-15 19:27 ` Mike Snitzer
2019-11-18 16:32 ` Alasdair G Kergon
2019-11-15 22:46 ` Stephen Rothwell
2019-11-15 23:10 ` Mike Snitzer
2019-11-15 23:32 ` Stephen Rothwell
2019-11-15 16:35 ` linux-next: Tree for Nov 15 (sound/soc/codecs/rt5677) Randy Dunlap
2019-11-15 23:44 ` linux-next: Tree for Nov 15 (thermal: THERMAL_GOV_POWER_ALLOCATOR) Randy Dunlap
2019-12-04 16:25 ` Randy Dunlap
2019-12-05 4:27 ` Zhang Rui
2019-12-05 4:36 ` Quentin Perret
2019-12-05 5:50 ` Zhang Rui
2019-12-05 5:47 ` Randy Dunlap
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=20200120153743.z6ws3jbgnsmsjvvx@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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