From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752236AbdCAOrR (ORCPT ); Wed, 1 Mar 2017 09:47:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41790 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751585AbdCAOrN (ORCPT ); Wed, 1 Mar 2017 09:47:13 -0500 Date: Wed, 1 Mar 2017 08:40:08 -0600 From: Josh Poimboeuf To: Arnd Bergmann Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, Linux Kernel Mailing List , Denys Vlasenko Subject: Re: [PATCH] [RFC] x86: avoid -mtune=atom for objtool warnings Message-ID: <20170301144008.3ocnbvry4sbl3cnu@treble> References: <20161010125709.1870563-1-arnd@arndb.de> <20161011150541.opini6gbolmnpzy5@treble> <20161011155146.icyl3zewdvmms2h2@treble> <2252957.Vm1BYSSRqP@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0.1 (2016-04-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Wed, 01 Mar 2017 14:40:11 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 01, 2017 at 10:45:03AM +0100, Arnd Bergmann wrote: > On Wed, Mar 1, 2017 at 10:34 AM, Arnd Bergmann wrote: > > On Tue, Oct 11, 2016 at 10:38 PM, Arnd Bergmann wrote: > >> On Tuesday, October 11, 2016 10:51:46 AM CEST Josh Poimboeuf wrote: > >>> > >>> 3) 0xFC244C03-config: > >>> drivers/scsi/fnic/fnic_main.o: warning: objtool: fnic_log_q_error() falls through to next function fnic_handle_link_event() > >>> drivers/scsi/snic/snic_res.o: warning: objtool: .text: unexpected end of section > >>> > >>> These look like another bad gcc bug which is truncating functions: > >> > >> Same bug for both of them? > > > > I ran into this one again today, after updating to the latest gcc-7.0.1: > > > > drivers/infiniband/sw/rxe/rxe_resp.o: warning: objtool: > > rxe_responder()+0xfe: sibling call from callable instruction with > > changed frame pointer > > > > Josh, did you get around to updating objtool the last time I reported it, or > > is it still the same problem? If this is a new variation, I can provide more > > details about the failure, otherwise I'll just ignore it for now. > > Actually, something must have changed in gcc since last month, I also > just got a report in another file: > > drivers/i2c/busses/i2c-img-scb.o: warning: objtool: img_i2c_probe() > falls through to next function img_i2c_read_fifo() This one looks like it could be related to some recent objtool changes which affect how it interprets 'ud2'. Which commit were you testing with? Can you provide the .config file, and the object file if it's not too big? -- Josh