From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753313AbeADQNL (ORCPT + 1 other); Thu, 4 Jan 2018 11:13:11 -0500 Received: from one.firstfloor.org ([193.170.194.197]:41888 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751523AbeADQNJ (ORCPT ); Thu, 4 Jan 2018 11:13:09 -0500 Date: Thu, 4 Jan 2018 08:13:08 -0800 From: Andi Kleen To: Josh Poimboeuf Cc: Andi Kleen , Andi Kleen , tglx@linutronix.de, torvalds@linux-foundation.org, gregkh@linux-foundation.org, linux-kernel@vger.kernel.org, tim.c.chen@linux.intel.com Subject: Re: [PATCH v2 11/12] retpoline/objtool: Disable some objtool warnings Message-ID: <20180104161308.zvudrggt6755ls5i@two.firstfloor.org> References: <20180104020019.1173-1-andi@firstfloor.org> <20180104020019.1173-12-andi@firstfloor.org> <20180104143814.bhvtsjiwpyhtgjph@treble> <20180104155914.GL25156@tassilo.jf.intel.com> <20180104160601.w2l2wdabuxa26xzq@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180104160601.w2l2wdabuxa26xzq@treble> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Thu, Jan 04, 2018 at 10:06:01AM -0600, Josh Poimboeuf wrote: > On Thu, Jan 04, 2018 at 07:59:14AM -0800, Andi Kleen wrote: > > > NAK. We can't blindly disable objtool warnings, that will break > > > livepatch and the ORC unwinder. If you share a .o file (or the GCC > > > code) I can look at adding retpoline support. > > > > I don't think we can wait for that. We can disable livepatch and the > > unwinder for now. They are not essential. Frame pointers should work > > well enough for unwinding > > If you want to make this feature conflict with livepatch and ORC, > silencing objtool warnings is not the way to do it. I don't see why it would conflict with the unwinder anyways? It doesn't change the long term stack state, so it should be invisible to the unwinder (unless you crash in the thunk, which is very unlikely) I actually got some unwinder backtraces during development and they seemed to work. > > > and afaik nobody can use livepatch in mainline anyways. > > Why not? The patch creation tooling is still out-of-tree, but livepatch > itself is fully supported in mainline. Ok. Still doesn't seem critical at this point if it's some out of tree thing. -Andi