From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: livepatching tree for linux-next Date: Wed, 7 Jan 2015 15:30:06 -0800 Message-ID: <20150107153006.60ed354e3458f402e6819b9e@linux-foundation.org> References: <20141223094607.GA16445@infradead.org> <20141223151056.GA4789@treble.redhat.com> <20141226155613.36dd95b9@canb.auug.org.au> <20150107144317.61ab2080877a4d8227990551@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Jiri Kosina Cc: Stephen Rothwell , Josh Poimboeuf , Christoph Hellwig , linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, linux-next@vger.kernel.org, Steven Rostedt , Masami Hiramatsu List-Id: linux-next.vger.kernel.org On Thu, 8 Jan 2015 00:01:02 +0100 (CET) Jiri Kosina wrote: > On Wed, 7 Jan 2015, Andrew Morton wrote: > > > > OK, I have added this from today > > > > My x86_64 allmodconfig broke. > > > > In file included from include/linux/livepatch.h:29, > > from kernel/livepatch/core.c:30: > > ./arch/x86/include/asm/livepatch.h:29:2: error: #error Your compiler must support -mfentry for live patching to work > > [ adding Steven and Masami to CC, as this in some sense is related in > both to ftrace regs caller, and to IPMODIFY users in general ] > > Well, if your gcc is too old (which is a fact detemined during build time, > so there is no way to express this in Kconfig language in form of > dependencies), we have to introduce build-time failure, as there is no way > for this to work on compilers that don't support fentry on x86_64. > > The only remaining option is to let the code build, pretend that > everything is working, but do something like > > #ifndef CC_USING_FENTRY > printk("The compiler you used to compile your kernel was ancient " > "there is no way for you to make use of this feature\n"); > return -EINVAL; > #endif > > or so ... which I personally detest even more. um, what's so special about this patchset that it gets to be the first code in the history of the kernel which breaks allmodconfig? Please find a way to fix it. Copying CONFIG_CC_STACKPROTECTOR is one way.