Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp2515757ybg; Fri, 31 Jul 2020 01:57:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwJnxORZGMsBay6TAi8JXoWcZIuHoFVcet1FCv9wgfWSWJM+3dUxBLoOL0ac8B7KQWsNgAd X-Received: by 2002:a17:906:e46:: with SMTP id q6mr3001638eji.234.1596185871150; Fri, 31 Jul 2020 01:57:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596185871; cv=none; d=google.com; s=arc-20160816; b=T5VRKhGi/UWPf6JGk2qurCTT8k6beDXJlAtclWCorqHILw+G+s9BPShHwCjZxELbPI CLusuh1rRucjVCyA5SCj6bBnGIVVNvGruNCxLjMOF97Y9V8qDpAT8CocxiGtdNhdet1Y j1gFpL2cUE/gcIt+08N3En+v80Ra3l4MKEvBwrwLV58+tA8qGs0FjWX4vabl739L6Ydx Zt9MkplG3Mj0ice9aJvafcG3UgA8bfX67BTaaowAx0TxZ13YzyjetOVX4mGCZBP/xpwI uM5UlduaXjQ+Vg4uOMyKvfhqsSOvcMAoHckTrTQ8zUrKAjPpTbJKPfal/hEaX8v42smQ /7yw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=F7PKRkqvsKufRE8aaUtDf3m+hNAgzvB1WlFGLHPhei4=; b=YxL6IvDn6XZIrGe8z3Pxuh5+B0i1W1YgwfSyO2wK9rGnkv3Y9GifkYGVvCkxjsqRm3 SIhnt/nbuCgZmfjeOI8g+U196M/en8tc++SvD4eFTo9Gc1JPJWQx6D8NRQR9zLl59SAT ObuoEeyQTQ4zYV947p2z+mwx1NDfLCDLPy50JL+VvsDeb7P36d4+pSuidU35GzYc++cR Xl0VOFuLBX3iy8Qj9m4qvzIsMO8Ui2449fHloLuS2/8qhXkAIQNY+O+k6tm776rPpn7q qsPMqZe59oEIY03D1KDZ1aJV2VPUFnEEcCMG0/mH9Qo1FzXbwepKSXzbNqa+iaeYTAAp Uq4A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o24si4194904eji.60.2020.07.31.01.57.29; Fri, 31 Jul 2020 01:57:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732029AbgGaI4Z (ORCPT + 99 others); Fri, 31 Jul 2020 04:56:25 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:50060 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730268AbgGaI4Z (ORCPT ); Fri, 31 Jul 2020 04:56:25 -0400 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 15A4E2E03E6C6E63C568; Fri, 31 Jul 2020 16:56:22 +0800 (CST) Received: from [127.0.0.1] (10.67.76.251) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.487.0; Fri, 31 Jul 2020 16:56:17 +0800 Subject: Re: linux-next: Tree for Jul 30 [build failure on arm64] To: Naresh Kamboju , Stephen Rothwell , Christoph Hellwig CC: Linux Next Mailing List , "Linux Kernel Mailing List" , Al Viro , "Arnd Bergmann" , References: <20200730214659.0fbfdfc4@canb.auug.org.au> <72b073ba-ee41-1a1c-ce6c-ffd8b5936b09@hisilicon.com> <20200731140842.46abe589@canb.auug.org.au> From: Shaokun Zhang Message-ID: <9b46f27a-2e5b-8519-31b6-01eaa9e1d822@hisilicon.com> Date: Fri, 31 Jul 2020 16:56:17 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.67.76.251] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, 在 2020/7/31 16:30, Naresh Kamboju 写道: > On Fri, 31 Jul 2020 at 09:38, Stephen Rothwell wrote: >> >> Hi all, >> >> On Fri, 31 Jul 2020 10:46:52 +0800 Shaokun Zhang wrote: >>> >>> There's a build failure on arm64: >>> >>> In file included from ./include/linux/compat.h:17:0, >>> from ./arch/arm64/include/asm/stat.h:13, >>> from ./include/linux/stat.h:6, >>> from ./include/linux/sysfs.h:22, >>> from ./include/linux/kobject.h:20, >>> from ./include/linux/of.h:17, >>> from ./include/linux/irqdomain.h:35, >>> from ./include/linux/acpi.h:13, >>> from ./include/acpi/apei.h:9, >>> from ./include/acpi/ghes.h:5, >>> from ./include/linux/arm_sdei.h:8, >>> from arch/arm64/kernel/asm-offsets.c:10: >>> ./include/linux/fs.h: In function ‘vfs_whiteout’: >>> ./include/linux/fs.h:1709:32: error: ‘S_IFCHR’ undeclared (first use in this function) >>> return vfs_mknod(dir, dentry, S_IFCHR | WHITEOUT_MODE, WHITEOUT_DEV); >>> ^ >>> ./include/linux/fs.h:1709:32: note: each undeclared identifier is reported only once for each >>> function it appears in >>> ./include/linux/fs.h: At top level: >>> ./include/linux/fs.h:1855:46: warning: ‘struct kstat’ declared inside parameter list >>> int (*getattr) (const struct path *, struct kstat *, u32, unsigned int); >>> ^ >>> ./include/linux/fs.h:1855:46: warning: its scope is only this definition or declaration, which is >>> probably not what you want >>> ./include/linux/fs.h: In function ‘__mandatory_lock’: >>> ./include/linux/fs.h:2325:25: error: ‘S_ISGID’ undeclared (first use in this function) >>> return (ino->i_mode & (S_ISGID | S_IXGRP)) == S_ISGID; >>> ^ >>> ./include/linux/fs.h:2325:35: error: ‘S_IXGRP’ undeclared (first use in this function) >>> return (ino->i_mode & (S_ISGID | S_IXGRP)) == S_ISGID; >>> ^ >>> ./include/linux/fs.h: In function ‘invalidate_remote_inode’: >>> ./include/linux/fs.h:2588:6: error: implicit declaration of function ‘S_ISREG’ >>> [-Werror=implicit-function-declaration] >>> if (S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) || >>> ^ >>> ./include/linux/fs.h:2588:32: error: implicit declaration of function ‘S_ISDIR’ >>> [-Werror=implicit-function-declaration] >>> if (S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) || >>> ^ >>> ./include/linux/fs.h:2589:6: error: implicit declaration of function ‘S_ISLNK’ >>> [-Werror=implicit-function-declaration] >>> S_ISLNK(inode->i_mode)) >>> ^ >>> ./include/linux/fs.h: In function ‘execute_ok’: >>> ./include/linux/fs.h:2768:26: error: ‘S_IXUGO’ undeclared (first use in this function) >>> return (inode->i_mode & S_IXUGO) || S_ISDIR(inode->i_mode); >> >> Presumably caused by commit >> >> b902bfb3f0e9 ("arm64: stop using directly") > > I have reverted this commit > b902bfb3f0e9 ("arm64: stop using directly") > > and rebuilt arm64 failed due to below errors/warnings. > > make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm64 > CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=gcc CC="sccache > aarch64-linux-gnu-gcc" O=build Image > # > In file included from ../include/linux/stat.h:6, > from ../include/linux/sysfs.h:22, > from ../include/linux/kobject.h:20, > from ../include/linux/of.h:17, > from ../include/linux/irqdomain.h:35, > from ../include/linux/acpi.h:13, > from ../include/acpi/apei.h:9, > from ../include/acpi/ghes.h:5, > from ../include/linux/arm_sdei.h:8, > from ../arch/arm64/kernel/asm-offsets.c:10: > ../arch/arm64/include/asm/stat.h:20:2: error: unknown type name ‘compat_u64’ > 20 | compat_u64 st_dev; > | 0a3a4497a1de <"compat: lift compat_s64 and compat_u64 to "> has removed the compat_s64 and compat_u64. Thanks, Shaokun ^~~~~~~~~~ > ../arch/arm64/include/asm/stat.h:31:2: error: unknown type name ‘compat_u64’ > 31 | compat_u64 st_rdev; > | ^~~~~~~~~~ > ../arch/arm64/include/asm/stat.h:34:2: error: unknown type name ‘compat_s64’ > 34 | compat_s64 st_size; > | ^~~~~~~~~~ > ../arch/arm64/include/asm/stat.h:36:2: error: unknown type name ‘compat_u64’ > 36 | compat_u64 st_blocks; /* Number of 512-byte blocks allocated. */ > | ^~~~~~~~~~ > ../arch/arm64/include/asm/stat.h:47:2: error: unknown type name ‘compat_u64’ > 47 | compat_u64 st_ino; > | ^~~~~~~~~~ > make[2]: *** [../scripts/Makefile.build:114: > arch/arm64/kernel/asm-offsets.s] Error 1 > > - Naresh > > . >