Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938664AbcKXKBZ (ORCPT ); Thu, 24 Nov 2016 05:01:25 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:35224 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S938442AbcKXKBW (ORCPT ); Thu, 24 Nov 2016 05:01:22 -0500 Date: Thu, 24 Nov 2016 21:01:01 +1100 From: Nicholas Piggin To: Arnd Bergmann Cc: Greg Kroah-Hartman , Ingo Molnar , Al Viro , Adam Borowski , Michal Marek , Philip Muller , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Linus Torvalds , Andrew Morton , Peter Zijlstra , linux-arch , linux-kbuild , Russell King Subject: Re: [PATCH] x86/kbuild: enable modversions for symbols exported from asm Message-ID: <20161124210101.76fc21ff@roar.ozlabs.ibm.com> In-Reply-To: <2648926.soV2DX4tAK@wuerfel> References: <20161123205338.GA12050@angband.pl> <20161124073639.GA12728@kroah.com> <20161124185322.1e2a492c@roar.ozlabs.ibm.com> <2648926.soV2DX4tAK@wuerfel> Organization: IBM X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2107 Lines: 44 On Thu, 24 Nov 2016 10:38:04 +0100 Arnd Bergmann wrote: > On Thursday, November 24, 2016 6:53:22 PM CET Nicholas Piggin wrote: > > > > > > > Google tells me > > > > Linus is not a neutral bystander on the topic of symbol versioning, so I'm > > > > bracing for a robust response (actually I don't much care either way, I'm > > > > happy to put a couple of bandaids on it and keep it going) > > > > > > There are tools that people are working on to make it more obvious where > > > API breaks happen by looking at the .o debug data instead of our crazy > > > current system (which is really better than nothing), perhaps we should > > > start using them instead? > > > > > > See here for more details about this: > > > https://kernel-recipes.org/en/2016/talks/would-an-abi-changes-visualization-tool-be-useful-to-linux-kernel-maintenance/ > > > > Hmm. I guess it's basically similar to modversions, so has downsides of not > > detecting a semantic change unless it changes the type. But still, if we could > > replace our custom code with a tool like this for modversions functionality, > > that alone would be a massive improvement. But requiring debug info might be > > a bit of a show stopper. I also don't know if that would handle asm functions. > > It's certainly not an option for v4.9 at this point. There is also no Yeah I wasn't suggesting that for 4.9, or 4.10 even. > realistic way we can get a correct asm/asm-prototypes.h for all the > other architectures in place. At the moment, powerpc is the only > one that actually works with modversions. > > We can either make CONFIG_MODVERSIONS a per-architecture opt-in > and let only the ones that have the header file select that, or > revert all of Al's original patches that moved the exports. alpha, m68k, s390, sparc, ia64 are affected and have no patch (or none I've been cc'ed on) for asm-prototypes.h. Doesn't seem infeasible to add them before 4.9, considering the fairly low risk of patch. Opt-in would be pointless IMO, might as well just revert the arch part of Al's patch instead. Thanks, Nick