From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: mmotm 2020-01-28-20-05 uploaded (objtool warnings)
Date: Wed, 29 Jan 2020 11:19:56 -0600 [thread overview]
Message-ID: <20200129171956.wlwz5gr6fva5iae7@treble> (raw)
In-Reply-To: <5f2400c0-3d9d-9bfd-315e-a26bedb165a7@infradead.org>
On Wed, Jan 29, 2020 at 08:43:35AM -0800, Randy Dunlap wrote:
> On 1/28/20 8:06 PM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2020-01-28-20-05 has been uploaded to
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > mmotm-readme.txt says
> >
> > README for mm-of-the-moment:
> >
> > http://www.ozlabs.org/~akpm/mmotm/
> >
> > This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> > more than once a week.
> >
>
> on x86_64: (duh)
>
> > gcc --version
> gcc (SUSE Linux) 7.5.0
>
>
> fs/namei.o: warning: objtool: do_renameat2()+0x46d: unreachable instruction
> kernel/exit.o: warning: objtool: __x64_sys_exit_group()+0x2b: unreachable instruction
> drivers/iio/adc/vf610_adc.o: warning: objtool: vf610_set_conversion_mode()+0x4e: unreachable instruction
>
>
> Full randconfig file is attached.
>
> Do you want the .o files, Josh?
I'm able to recreate with your config, so I don't need the .o files.
Thanks.
--
Josh
prev parent reply other threads:[~2020-01-29 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 4:06 mmotm 2020-01-28-20-05 uploaded akpm
2020-01-29 4:39 ` mmotm 2020-01-28-20-05 uploaded (net/mptcp/subflow.c) Randy Dunlap
2020-01-29 4:52 ` mmotm 2020-01-28-20-05 uploaded (security/security.c) Randy Dunlap
2020-01-29 13:51 ` Paul Moore
2020-01-29 16:02 ` Randy Dunlap
2020-01-29 22:32 ` Stephen Rothwell
2020-01-29 16:43 ` mmotm 2020-01-28-20-05 uploaded (objtool warnings) Randy Dunlap
2020-01-29 17:19 ` Josh Poimboeuf [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=20200129171956.wlwz5gr6fva5iae7@treble \
--to=jpoimboe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.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).