From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5FF8FC00319 for ; Thu, 21 Feb 2019 08:04:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3CCA32086C for ; Thu, 21 Feb 2019 08:04:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727112AbfBUIEH convert rfc822-to-8bit (ORCPT ); Thu, 21 Feb 2019 03:04:07 -0500 Received: from mail-vs1-f65.google.com ([209.85.217.65]:44824 "EHLO mail-vs1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725385AbfBUIEH (ORCPT ); Thu, 21 Feb 2019 03:04:07 -0500 Received: by mail-vs1-f65.google.com with SMTP id r201so15619129vsc.11; Thu, 21 Feb 2019 00:04:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=RnKcTm27rROkKZMrhUWWs+Jztu9yzz/K7kE3s9xRNGA=; b=akYSMff7xdaVZmj0HYDcv7418FwPQQOKA+9DfWNAJAzLoQZ+CDih/Ll684yGB/1oWQ 40FD5HZdCwh1+aBFRHt4wzIFxfOGKHaxXgMuKdXX7WcoqNtvgBi06YaRV+j5FDLcEJf9 NCc37rYA9e4cZuIdm70jAUShOZZpGfnXz4Vi/vABkEP6GMRTflQY1AyhbqJTolDo6piy SJTeSNTcp6nsvLzKK6pqkCwTwOhb2/ZUjzNiRTVeXngq9ueNbeQQF+gzl5b6RQqKn/pl 6SXlUf6ToKlktfnlkl73m8/hSMsQWa4tbyaEUlR9cJS3KZ9cL4/C2M59HEbZndHWaIxl m9YA== X-Gm-Message-State: AHQUAubtuhoESFZggMuhQYPAt+yK8q/A60zDEvFpV7/zhuTgMJiY5Msx ypfu7fZ/na9zlTzOxt432ByySEltUV4og92cVGM= X-Google-Smtp-Source: AHgI3IYC+aTzKDq+KHRtT9UCaG2gOadnobKVXDd1kcKcujrgSh5A1Ebf5pKk68xHqQGUEluGcW+xavSJjfkc/vGsX90= X-Received: by 2002:a67:78ce:: with SMTP id t197mr19687673vsc.152.1550736245468; Thu, 21 Feb 2019 00:04:05 -0800 (PST) MIME-Version: 1.0 References: <20190220184341.73bd2084@canb.auug.org.au> <1114b964-8ff8-5632-64d4-e94a9160b998@hisilicon.com> <20190220095252.GA9089@linux.intel.com> <20190220095806.GB9089@linux.intel.com> In-Reply-To: From: Geert Uytterhoeven Date: Thu, 21 Feb 2019 09:03:52 +0100 Message-ID: Subject: Re: linux-next: Tree for Feb 20 To: Zhangshaokun Cc: Ard Biesheuvel , Jarkko Sakkinen , Mimi Zohar , Stephen Rothwell , Linux Next Mailing List , Roberto Sassu , Linux Kernel Mailing List , linux-efi , linux-integrity Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Shaokun, On Thu, Feb 21, 2019 at 1:45 AM Zhangshaokun wrote: > On 2019/2/20 18:05, Ard Biesheuvel wrote: > > On Wed, 20 Feb 2019 at 10:58, Jarkko Sakkinen > > wrote: > >> > >> On Wed, Feb 20, 2019 at 11:52:52AM +0200, Jarkko Sakkinen wrote: > >>> On Wed, Feb 20, 2019 at 05:11:15PM +0800, Zhangshaokun wrote: > >>>> There is a compiler failure on arm64 platform, as follow: > >>>> > >>>> AS arch/arm64/kvm/hyp.o > >>>> CC kernel/trace/ring_buffer.o > >>>> In file included from security/integrity/ima/ima_fs.c:30:0: > >>>> security/integrity/ima/ima.h:176:7: error: redeclaration of enumerator ‘NONE’ > >>>> hook(NONE) \ > >>>> ^ > >>>> security/integrity/ima/ima.h:188:34: note: in definition of macro ‘__ima_hook_enumify’ > >>>> #define __ima_hook_enumify(ENUM) ENUM, > >>>> ^ > >>>> security/integrity/ima/ima.h:191:2: note: in expansion of macro ‘__ima_hooks’ > >>>> __ima_hooks(__ima_hook_enumify) > >>>> ^ > >>>> In file included from ./arch/arm64/include/asm/acpi.h:15:0, > >>>> from ./include/acpi/acpi_io.h:7, > >>>> from ./include/linux/acpi.h:47, > >>>> from ./include/linux/tpm.h:26, > >>>> from security/integrity/ima/ima.h:25, > >>>> from security/integrity/ima/ima_fs.c:30: > >>>> ./include/linux/efi.h:1716:2: note: previous definition of ‘NONE’ was here > >>>> NONE, > >>>> ^ > >>>> scripts/Makefile.build:276: recipe for target 'security/integrity/ima/ima_fs.o' failed > >>>> make[3]: *** [security/integrity/ima/ima_fs.o] Error 1 > >>>> > >>>> I dug it and it is the commit 901615cb916d ("tpm: move tpm_chip definition to include/linux/tpm.h") > >>> > >>> This results from a new include in tpm.h: > >>> > >>> #include > >>> > >>> Must be fixed either in include/linux/efi.h or security/integrity/ima.h as > >>> those files have a name collision. Makes me wonder why neither has taken > >>> care of prefixing the constants properly. > >> > >> Preferably both subsystems should be fixed with proper 'EFI_' and 'IMA_' > >> prefixes. Defining a constant named as NONE in a non-generic subsystem > >> (e.g. not part of the core data structures of Linux) and especially > >> exporting it to include/linux is not too well considered act. > >> > > > > Fixes for this have already been proposed, and should appear in -next shortly > > > > The EFI one is here > > https://mail.google.com/mail/u/0/#label/linux-efi/FMfcgxwBVgrQRjglPkWRqRqVclGgVDnB > > > > Because of no privilege, the website is denied for me. Anyway, it's nice to have been fixed. Looks like Ard posted a link to a label in his personal gmail mailbox? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds