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>,
Miroslav Benes <mbenes@suse.cz>
Subject: Re: linux-next: Tree for May 21 (objtool warnings)
Date: Fri, 22 May 2020 11:34:38 -0500 [thread overview]
Message-ID: <20200522163438.s6klcxhdduljg2d5@treble> (raw)
In-Reply-To: <22332d9b-5e9f-5474-adac-9b3e39861aee@infradead.org>
On Thu, May 21, 2020 at 07:34:38PM -0700, Randy Dunlap wrote:
> On 5/21/20 7:12 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200519:
> >
>
> on x86_64:
>
> fs/open.o: warning: objtool: chmod_common()+0x104: unreachable instruction
> fs/namei.o: warning: objtool: do_renameat2()+0x482: unreachable instruction
> kernel/exit.o: warning: objtool: __ia32_sys_exit_group()+0x2e: unreachable instruction
>
>
> Full randconfig file is attached.
I think these are more -flive-patching related warnings. Adding
Miroslav in case he gets to fixing them before I do :-)
--
Josh
next prev parent reply other threads:[~2020-05-22 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 14:12 linux-next: Tree for May 21 Stephen Rothwell
2020-05-21 15:09 ` Daniel Thompson
2020-05-22 2:34 ` linux-next: Tree for May 21 (objtool warnings) Randy Dunlap
2020-05-22 16:34 ` Josh Poimboeuf [this message]
2020-05-25 10:10 ` Miroslav Benes
2020-05-25 11:07 ` Miroslav Benes
2020-05-26 14:01 ` Josh Poimboeuf
2020-05-26 16:39 ` Miroslav Benes
2020-05-27 8:57 ` Martin Jambor
2020-05-27 15:09 ` Josh Poimboeuf
2020-05-25 18:04 ` 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=20200522163438.s6klcxhdduljg2d5@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mbenes@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).