From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Mar 20 (objtool warnings)
Date: Fri, 20 Mar 2020 10:43:05 -0700 [thread overview]
Message-ID: <ca0078e2-89b5-09a7-f61e-7f2906900622@infradead.org> (raw)
In-Reply-To: <20200320201539.3a3a8640@canb.auug.org.au>
On 3/20/20 2:15 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200319:
>
Today's linux-next gives these objtool warnings:
arch/x86/entry/vdso/vma.o: warning: objtool: vdso_fault()+0x201: unreachable instruction
drivers/ide/ide-tape.o: warning: objtool: idetape_chrdev_release()+0x109: unreachable instruction
drivers/media/i2c/ir-kbd-i2c.o: warning: objtool: ir_probe()+0xdaa: unreachable instruction
kernel/kcov.o: warning: objtool: __sanitizer_cov_trace_pc()+0x89: call to __ubsan_handle_load_invalid_value() with UACCESS enabled
all in (4) separate builds (.configs).
Do you want all 4 randconfig files?
cheers.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-03-20 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 9:15 linux-next: Tree for Mar 20 Stephen Rothwell
2020-03-20 16:11 ` linux-next: Tree for Mar 20 (drivers/media/i2c/video-i2c.o) Randy Dunlap
2020-03-21 7:02 ` Matt Ranostay
2020-03-20 17:43 ` Randy Dunlap [this message]
2020-03-24 16:47 ` linux-next: Tree for Mar 20 (objtool warnings) Josh Poimboeuf
2020-03-24 17:53 ` Randy Dunlap
2020-03-24 21:13 ` Peter Zijlstra
2020-03-24 23:02 ` Andrey Konovalov
2020-03-26 14:45 ` Andrey Konovalov
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=ca0078e2-89b5-09a7-f61e-7f2906900622@infradead.org \
--to=rdunlap@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.