Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760618Ab2FDOhD (ORCPT ); Mon, 4 Jun 2012 10:37:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:27223 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754489Ab2FDOhB (ORCPT ); Mon, 4 Jun 2012 10:37:01 -0400 Date: Mon, 4 Jun 2012 10:36:43 -0400 From: Don Zickus To: Witold Baryluk Cc: linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org Subject: Re: WARNING: arch/x86/built-in.o: Section mismatch in reference from the variable test_nmi_ipi_callback_na to function .ini.text:test_nmi_ipi_callback Message-ID: <20120604143643.GJ32472@redhat.com> References: <20120602161502.GW16584@smp.if.uj.edu.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120602161502.GW16584@smp.if.uj.edu.pl> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3122 Lines: 79 On Sat, Jun 02, 2012 at 06:15:02PM +0200, Witold Baryluk wrote: > Hello everybody, > > x86 32-bit Build just got 2 WARNINGS when building kernel on Linus' tree. Hi Witold, Thanks for the warnings. > > > VDSOSYM arch/x86/vdso/vdso32-syms.lds > LD arch/x86/vdso/built-in.o > LD arch/x86/built-in.o > WARNING: arch/x86/built-in.o(.data+0x5af0): Section mismatch in reference from the variable test_nmi_ipi_callback_na.10451 to the function .init.text:test_nmi_ipi_callback() > The variable test_nmi_ipi_callback_na.10451 references > the function __init test_nmi_ipi_callback() > If the reference is valid then annotate the > variable with __init* or __refdata (see linux/init.h) or name the variable: > *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console > > WARNING: arch/x86/built-in.o(.data+0x5b04): Section mismatch in reference from the variable nmi_unk_cb_na.10399 to the function .init.text:nmi_unk_cb() > The variable nmi_unk_cb_na.10399 references > the function __init nmi_unk_cb() > If the reference is valid then annotate the > variable with __init* or __refdata (see linux/init.h) or name the variable: > *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console These are intermediate variables test_nmi_ipi_callback_na.10451 and nmi_unk_cb_na.10399. I do not know how to fix them. Basically the test registers two nmi_handlers, run some tests, and then unregisters them. Those handlers are what the compiler seems to be complaining about. I do not know what magic to pass the compiler to let it know that both of the handlers will be unregistered before the init section is destroyed. Perhaps I should tag those callbacks with __ref? I am not sure the right thing to do here. Cheers, Don > > LD vmlinux.o > MODPOST vmlinux.o > WARNING: vmlinux.o(.data+0x7cf0): Section mismatch in reference from the variable test_nmi_ipi_callback_na.10451 to the function .init.text:test_nmi_ipi_callback() > The variable test_nmi_ipi_callback_na.10451 references > the function __init test_nmi_ipi_callback() > If the reference is valid then annotate the > variable with __init* or __refdata (see linux/init.h) or name the variable: > *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console > > WARNING: vmlinux.o(.data+0x7d04): Section mismatch in reference from the variable nmi_unk_cb_na.10399 to the function .init.text:nmi_unk_cb() > The variable nmi_unk_cb_na.10399 references > the function __init nmi_unk_cb() > If the reference is valid then annotate the > variable with __init* or __refdata (see linux/init.h) or name the variable: > *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console > > GEN .version > CHK include/generated/compile.h > > > > > This is recent change. > > gcc version 4.7.0 (Debian 4.7.0-11) > > Debian sid, i386. > > -- > Witold Baryluk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/