From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752070AbcKUFuB (ORCPT ); Mon, 21 Nov 2016 00:50:01 -0500 Received: from mail-pg0-f67.google.com ([74.125.83.67]:36125 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750744AbcKUFt7 (ORCPT ); Mon, 21 Nov 2016 00:49:59 -0500 Date: Mon, 21 Nov 2016 16:49:40 +1100 From: Nicholas Piggin To: Peter Wu Cc: Vince Weaver , Michal Marek , Al Viro , Oliver Hartkopp , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, linux-arch@vger.kernel.org, regressions@leemhuis.info, Adam Borowski Subject: Re: 'kbuild' merge before 4.9-rc1 breaks build and boot Message-ID: <20161121164940.33b555ea@roar.ozlabs.ibm.com> In-Reply-To: <20161120182623.GA1988@al> References: <4c04b846-3da8-dc42-4fa6-30f72a5c2437@hartkopp.net> <20161027154202.GE27017@al> <20161107213907.GB18092@al> <20161108123334.3df2dcc9@roar.ozlabs.ibm.com> <20161120182623.GA1988@al> 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 On Sun, 20 Nov 2016 19:26:23 +0100 Peter Wu wrote: > Hi Nicholas, > > Current git master (v4.9-rc5-364-g77079b1) with the latest kbuild fixes > is still failing to load modules when built with CONFIG_MODVERSIONS=y on > x86_64 using GCC 6.2.1. > > It can still be reproduced with make defconfig, then enabling > CONFIG_MODVERSIONS=y. The build output contains: > > WARNING: "memcpy" [net/netfilter/nf_nat.ko] has no CRC! > WARNING: "memmove" [net/netfilter/nf_nat.ko] has no CRC! > WARNING: "_copy_to_user" [fs/efivarfs/efivarfs.ko] has no CRC! > WARNING: "memcpy" [fs/efivarfs/efivarfs.ko] has no CRC! > WARNING: "_copy_from_user" [fs/efivarfs/efivarfs.ko] has no CRC! Hi Peter, Sorry it's taken some time, bear with us. The arch specific patches need to be merged now. Adam, what is the status of your patch? Please submit to x86 maintainers if you haven't already. Thanks, Nick