Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 24 Mar 2020 11:47:09 -0500
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 Mar 20 (objtool warnings)
Message-ID: <20200324164709.ux4riz7v7uy32nlj@treble>
References: <20200320201539.3a3a8640@canb.auug.org.au>
 <ca0078e2-89b5-09a7-f61e-7f2906900622@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <ca0078e2-89b5-09a7-f61e-7f2906900622@infradead.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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
> 
> 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?

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.

-- 
Josh