From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A19D118D for ; Wed, 6 Apr 2022 01:32:58 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4AB92C385AD for ; Wed, 6 Apr 2022 01:32:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649208778; bh=XpvRyWQibs5U7H0NRwftD7kh9ztYJOg4NmB70y/JR0c=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=BUidOn6eR29LJmE2NHApcc449KHBc1lxLFlFrYVlnFeV+tyqGdB42oP4tC5ZTeP/R UcWKho4QCrgsem7C166iXrO68B+2bTBBJqm6cV3VzkBRJvbOwPcKLcH4lSZV6J6XdT jrMKQu+rMK8lpeQUC3aYQD53q4P2IUEqhHd4JjZvi4QJopmyMZG1LRUbf+p2XiAIqs SKptDQG83bXtk2JUkH1EHs0WAr7+4VhIEKk3RlRWnOcZxfPb7GJHlTFjDLWhHManLG LIR8b4E4sm6+zq5FUl6xnGii1j+I4gMZZBrMsfuhq8FKYbbBpltRrfG782f3MvDELk QiJjQo0p8vosA== Received: by mail-vk1-f173.google.com with SMTP id b81so470506vkf.1 for ; Tue, 05 Apr 2022 18:32:58 -0700 (PDT) X-Gm-Message-State: AOAM53116jA6pmJpkKl9IeJsFyzfwRWg6v5cH6vUzSPD0B/jvoOh/NqB S2CsvjGYvSemLyWzwmILoynB8xVqQZnVQIBU/q4= X-Google-Smtp-Source: ABdhPJzav7/zsbYcqRTWKyLRMmW/wUoG3z2ctFpfrzr8BqmpNb/HTabQkiDzQ/qWUmxCkD3Sp5ceqOVOwtSovwFqWmg= X-Received: by 2002:a1f:f283:0:b0:33f:5e3e:921b with SMTP id q125-20020a1ff283000000b0033f5e3e921bmr2261970vkh.2.1649208777147; Tue, 05 Apr 2022 18:32:57 -0700 (PDT) Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: In-Reply-To: From: Guo Ren Date: Wed, 6 Apr 2022 09:32:46 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed. To: Palmer Dabbelt Cc: Nathan Chancellor , Naresh Kamboju , Linux Next Mailing List , Linux Kernel Mailing List , linux-riscv , lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Stephen Rothwell , Guo Ren , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Arnd Bergmann , Paul Walmsley , Albert Ou Content-Type: text/plain; charset="UTF-8" On Wed, Apr 6, 2022 at 9:13 AM Guo Ren wrote: > > On Wed, Apr 6, 2022 at 12:15 AM Palmer Dabbelt wrote: > > > > On Mon, 04 Apr 2022 22:17:24 PDT (-0700), guoren@kernel.org wrote: > > > On Tue, Apr 5, 2022 at 12:57 AM Nathan Chancellor wrote: > > >> > > >> On Mon, Apr 04, 2022 at 03:28:41PM +0530, Naresh Kamboju wrote: > > >> > Linux next-20220404 riscv defconfig builds failed. > > >> > > > >> > Regressions found on riscv: > > >> > - riscv-riscv-clang-14-defconfig > > >> > - riscv-riscv-gcc-10-defconfig > > >> > - riscv-riscv-clang-13-defconfig > > >> > - riscv-riscv-clang-12-defconfig > > >> > - riscv-riscv-clang-11-defconfig > > >> > - riscv-riscv-gcc-11-defconfig > > >> > - riscv-riscv-gcc-8-defconfig > > >> > - riscv-riscv-gcc-9-defconfig > > >> > - riscv-riscv-clang-nightly-defconfig > > >> > > > >> > > > >> > arch/riscv/kernel/compat_signal.c:7:10: fatal error: > > >> > linux/tracehook.h: No such file or directory > > >> > 7 | #include > > >> > | ^~~~~~~~~~~~~~~~~~~ > > >> > compilation terminated. > > >> > make[3]: *** [scripts/Makefile.build:289: > > >> > arch/riscv/kernel/compat_signal.o] Error 1 > > >> > > >> For what it's worth, I also see: > > >> > > >> $ make -skj"$(nproc)" ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- defconfig all > > >> arch/riscv/kernel/compat_vdso/compat_vdso.lds.S:3:10: fatal error: ../vdso/vdso.lds.S: No such file or directory > > >> 3 | #include <../vdso/vdso.lds.S> > > >> | ^~~~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> make[2]: *** [scripts/Makefile.build:462: arch/riscv/kernel/compat_vdso/compat_vdso.lds] Error 1 > > >> arch/riscv/kernel/compat_vdso/rt_sigreturn.S:3:10: fatal error: ../vdso/rt_sigreturn.S: No such file or directory > > >> 3 | #include <../vdso/rt_sigreturn.S> > > >> | ^~~~~~~~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> arch/riscv/kernel/compat_vdso/note.S:3:10: fatal error: ../vdso/note.S: No such file or directory > > >> 3 | #include <../vdso/note.S> > > >> | ^~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> arch/riscv/kernel/compat_vdso/getcpu.S:3:10: fatal error: ../vdso/getcpu.S: No such file or directory > > >> 3 | #include <../vdso/getcpu.S> > > >> | ^~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/rt_sigreturn.o] Error 1 > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/note.o] Error 1 > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/getcpu.o] Error 1 > > >> arch/riscv/kernel/compat_vdso/flush_icache.S:3:10: fatal error: ../vdso/flush_icache.S: No such file or directory > > >> 3 | #include <../vdso/flush_icache.S> > > >> | ^~~~~~~~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/flush_icache.o] Error 1 > > >> > > >> I am guessing this code was never tested with $(srctree) == $(objtree). > > > Thx for pointing it out: > > > I always use: > > > make -skj"$(nproc)" ARCH=riscv > > > CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g > > > O=../build-riscv/ defconfig all > > > > > > When I change to: > > > make -skj"$(nproc)" ARCH=riscv > > > CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g defconfig > > > all > > > > > > I got your problem. > > > > Just to be clear: this one wasn't supposed to go in via the csky tree, > > and had other build issues that were being found by the autobuilders > > (which is why it hadn't gone in via the riscv tree). I do in-tree > > builds somewhat regularly so that probably would have caught it if > > nothing else did, but my guess is that some other autobuilder would have > > found it first (some of the earlier patches > The problem and other build issues (arm64 & 5.18-rc1 conflict) all > have been solved in v12: > https://lore.kernel.org/linux-riscv/20220405071314.3225832-1-guoren@kernel.org/ > > > > > Guo: please stop pushing things to linux-next that break the builds > > and/or aren't aimed at your tree. This just makes things unnecessarly > > complicated. If you don't want to deal with the build issues that's OK, > > just LMK when you send the patch sets out and I'll deal with them, but If you could deal with build issues that would be very thankful. I just hope these patch series could get into for-next earlier before the next merge window. So I utilized next-tree-20220404 to find out what problems with that (of course these patches should be from your tree). The autobuilder for next-tree is more strict, and now seems almost all problems have been solved. > > having linux-next's build break causes fallout for a lot of users. > Yesterday, I made my > https://github.com/c-sky/csky-linux/commits/linux-next with > linux-5.18-rc1 tag commit version. > So this only affected linux-next-20220404. > > > -- > Best Regards > Guo Ren > > ML: https://lore.kernel.org/linux-csky/ -- Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/ 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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B9D95C433EF for ; Wed, 6 Apr 2022 01:33:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=wc6ihdQ97nwJLOizeOLp9DWS+fGdS7t93qLlOfrYjcE=; b=iVMrmr6WRF9lCT CPWayvChPeV9Nd3clhT3YVf0m9rBg5bTv4yHo20OBjUB8VpfOKVmr0IheRJsLjuo5x+QTyqG7To+U LYS35xQ84Fs/PlGQmDtA4jM/GxDoQ0pn+Ym5SNF0SrCp0QHmWiSLZ61AAoyzmZbBRkL0q0PV4gZCQ FSdHRoE9I8sH3pmlE42HmvLvsYH/lQ2H4U+oOyalDZbcPUvwqlrROy+RMVLasEl/k2AwEhKQAK72+ YZ46uJs/j/n9Q6EYb7cMoUtavzZgbGC8fK9li3Bc96UsA1tdYxOHtIso8gwusj9h07DZ43Su9dn+M oEPlkexH3v2n+KWCuebQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nbuXe-003Eqj-VC; Wed, 06 Apr 2022 01:33:02 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nbuXc-003Eq4-31 for linux-riscv@lists.infradead.org; Wed, 06 Apr 2022 01:33:01 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6251861AF8 for ; Wed, 6 Apr 2022 01:32:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 42E0FC385A9 for ; Wed, 6 Apr 2022 01:32:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649208778; bh=XpvRyWQibs5U7H0NRwftD7kh9ztYJOg4NmB70y/JR0c=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=BUidOn6eR29LJmE2NHApcc449KHBc1lxLFlFrYVlnFeV+tyqGdB42oP4tC5ZTeP/R UcWKho4QCrgsem7C166iXrO68B+2bTBBJqm6cV3VzkBRJvbOwPcKLcH4lSZV6J6XdT jrMKQu+rMK8lpeQUC3aYQD53q4P2IUEqhHd4JjZvi4QJopmyMZG1LRUbf+p2XiAIqs SKptDQG83bXtk2JUkH1EHs0WAr7+4VhIEKk3RlRWnOcZxfPb7GJHlTFjDLWhHManLG LIR8b4E4sm6+zq5FUl6xnGii1j+I4gMZZBrMsfuhq8FKYbbBpltRrfG782f3MvDELk QiJjQo0p8vosA== Received: by mail-vk1-f173.google.com with SMTP id w189so449691vke.10 for ; Tue, 05 Apr 2022 18:32:58 -0700 (PDT) X-Gm-Message-State: AOAM532Ezd29P+NHdlWd0bKu1G7leE1cQvNBCCVQoEPowgAMTHI93RUr 0D6chPLG9xtTDhwdf1OQJtxaF/se0vTWwDrQzGM= X-Google-Smtp-Source: ABdhPJzav7/zsbYcqRTWKyLRMmW/wUoG3z2ctFpfrzr8BqmpNb/HTabQkiDzQ/qWUmxCkD3Sp5ceqOVOwtSovwFqWmg= X-Received: by 2002:a1f:f283:0:b0:33f:5e3e:921b with SMTP id q125-20020a1ff283000000b0033f5e3e921bmr2261970vkh.2.1649208777147; Tue, 05 Apr 2022 18:32:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Guo Ren Date: Wed, 6 Apr 2022 09:32:46 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [next] riscv: Linux next-20220404 riscv defconfig builds failed. To: Palmer Dabbelt Cc: Nathan Chancellor , Naresh Kamboju , Linux Next Mailing List , Linux Kernel Mailing List , linux-riscv , lkft-triage@lists.linaro.org, regressions@lists.linux.dev, Stephen Rothwell , Guo Ren , =?UTF-8?Q?Heiko_St=C3=BCbner?= , Arnd Bergmann , Paul Walmsley , Albert Ou X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220405_183300_251305_E0428961 X-CRM114-Status: GOOD ( 32.80 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On Wed, Apr 6, 2022 at 9:13 AM Guo Ren wrote: > > On Wed, Apr 6, 2022 at 12:15 AM Palmer Dabbelt wrote: > > > > On Mon, 04 Apr 2022 22:17:24 PDT (-0700), guoren@kernel.org wrote: > > > On Tue, Apr 5, 2022 at 12:57 AM Nathan Chancellor wrote: > > >> > > >> On Mon, Apr 04, 2022 at 03:28:41PM +0530, Naresh Kamboju wrote: > > >> > Linux next-20220404 riscv defconfig builds failed. > > >> > > > >> > Regressions found on riscv: > > >> > - riscv-riscv-clang-14-defconfig > > >> > - riscv-riscv-gcc-10-defconfig > > >> > - riscv-riscv-clang-13-defconfig > > >> > - riscv-riscv-clang-12-defconfig > > >> > - riscv-riscv-clang-11-defconfig > > >> > - riscv-riscv-gcc-11-defconfig > > >> > - riscv-riscv-gcc-8-defconfig > > >> > - riscv-riscv-gcc-9-defconfig > > >> > - riscv-riscv-clang-nightly-defconfig > > >> > > > >> > > > >> > arch/riscv/kernel/compat_signal.c:7:10: fatal error: > > >> > linux/tracehook.h: No such file or directory > > >> > 7 | #include > > >> > | ^~~~~~~~~~~~~~~~~~~ > > >> > compilation terminated. > > >> > make[3]: *** [scripts/Makefile.build:289: > > >> > arch/riscv/kernel/compat_signal.o] Error 1 > > >> > > >> For what it's worth, I also see: > > >> > > >> $ make -skj"$(nproc)" ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- defconfig all > > >> arch/riscv/kernel/compat_vdso/compat_vdso.lds.S:3:10: fatal error: ../vdso/vdso.lds.S: No such file or directory > > >> 3 | #include <../vdso/vdso.lds.S> > > >> | ^~~~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> make[2]: *** [scripts/Makefile.build:462: arch/riscv/kernel/compat_vdso/compat_vdso.lds] Error 1 > > >> arch/riscv/kernel/compat_vdso/rt_sigreturn.S:3:10: fatal error: ../vdso/rt_sigreturn.S: No such file or directory > > >> 3 | #include <../vdso/rt_sigreturn.S> > > >> | ^~~~~~~~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> arch/riscv/kernel/compat_vdso/note.S:3:10: fatal error: ../vdso/note.S: No such file or directory > > >> 3 | #include <../vdso/note.S> > > >> | ^~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> arch/riscv/kernel/compat_vdso/getcpu.S:3:10: fatal error: ../vdso/getcpu.S: No such file or directory > > >> 3 | #include <../vdso/getcpu.S> > > >> | ^~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/rt_sigreturn.o] Error 1 > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/note.o] Error 1 > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/getcpu.o] Error 1 > > >> arch/riscv/kernel/compat_vdso/flush_icache.S:3:10: fatal error: ../vdso/flush_icache.S: No such file or directory > > >> 3 | #include <../vdso/flush_icache.S> > > >> | ^~~~~~~~~~~~~~~~~~~~~~~~ > > >> compilation terminated. > > >> make[2]: *** [arch/riscv/kernel/compat_vdso/Makefile:43: arch/riscv/kernel/compat_vdso/flush_icache.o] Error 1 > > >> > > >> I am guessing this code was never tested with $(srctree) == $(objtree). > > > Thx for pointing it out: > > > I always use: > > > make -skj"$(nproc)" ARCH=riscv > > > CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g > > > O=../build-riscv/ defconfig all > > > > > > When I change to: > > > make -skj"$(nproc)" ARCH=riscv > > > CROSS_COMPILE=riscv64-unknown-linux-gnu- EXTRA_CFLAGS+=-g defconfig > > > all > > > > > > I got your problem. > > > > Just to be clear: this one wasn't supposed to go in via the csky tree, > > and had other build issues that were being found by the autobuilders > > (which is why it hadn't gone in via the riscv tree). I do in-tree > > builds somewhat regularly so that probably would have caught it if > > nothing else did, but my guess is that some other autobuilder would have > > found it first (some of the earlier patches > The problem and other build issues (arm64 & 5.18-rc1 conflict) all > have been solved in v12: > https://lore.kernel.org/linux-riscv/20220405071314.3225832-1-guoren@kernel.org/ > > > > > Guo: please stop pushing things to linux-next that break the builds > > and/or aren't aimed at your tree. This just makes things unnecessarly > > complicated. If you don't want to deal with the build issues that's OK, > > just LMK when you send the patch sets out and I'll deal with them, but If you could deal with build issues that would be very thankful. I just hope these patch series could get into for-next earlier before the next merge window. So I utilized next-tree-20220404 to find out what problems with that (of course these patches should be from your tree). The autobuilder for next-tree is more strict, and now seems almost all problems have been solved. > > having linux-next's build break causes fallout for a lot of users. > Yesterday, I made my > https://github.com/c-sky/csky-linux/commits/linux-next with > linux-5.18-rc1 tag commit version. > So this only affected linux-next-20220404. > > > -- > Best Regards > Guo Ren > > ML: https://lore.kernel.org/linux-csky/ -- Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/ _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv