[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39035493-9d5b-9da3-10d4-0af5d1cdb32a@infradead.org>
Date: Tue, 24 Mar 2020 10:53:05 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: linux-next: Tree for Mar 20 (objtool warnings)
On 3/24/20 9:47 AM, Josh Poimboeuf wrote:
> On Fri, Mar 20, 2020 at 10:43:05AM -0700, Randy Dunlap wrote:
>> 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
has CONFIG_UBSAN_TRAP=y
>> drivers/ide/ide-tape.o: warning: objtool: idetape_chrdev_release()+0x109: unreachable instruction
ditto
>> drivers/media/i2c/ir-kbd-i2c.o: warning: objtool: ir_probe()+0xdaa: unreachable instruction
ditto.
>> kernel/kcov.o: warning: objtool: __sanitizer_cov_trace_pc()+0x89: call to __ubsan_handle_load_invalid_value() with UACCESS enabled
>>
config-r1510 is attached.
and kcov.o is attached.
>>
>> all in (4) separate builds (.configs).
>> Do you want all 4 randconfig files?
>
> For the "unreachable instruction" warnings, if the configs have
> CONFIG_UBSAN_TRAP, that's a known issue.
>
> Otherwise, yeah, configs (and .o files if possible) would be good.
cheers.
--
~Randy
View attachment "config-r1510" of type "text/plain" (107928 bytes)
Download attachment "kcov.o" of type "application/x-object" (98440 bytes)
Powered by blists - more mailing lists