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 A04AF257828 for ; Mon, 17 Nov 2025 13:30:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763386246; cv=none; b=ImaGHrFrfqua/rccU7Re4SH3cwh73bvMf+9cwWgaKyyiroxVmuY5gfA6VXSLZGmHS+WXTFF5HNt11lhPFtil1cCc2DfQZUNfrJJIAwoRbF01U1HNhx47P7tAl3zA1StGzUpJBh4YaQuSD3x/kooMQeqlJIax+WVfhtXYmFqjfqA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763386246; c=relaxed/simple; bh=xMhINDDZUPo36kUXPr6r5jMYBQ/OrCLLJKAlTYK573E=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=fS9UjicwYhZaLdZyyTxIhJJ2ECzcDPLV/VeAYQpIcugPHbC7GxTBlMWfFfDywl2ngxuqPTx9ie8aJs2mYgOFxNOggd4VcD+9Flg9FX5eqtxrhBjUs7J5oeAAOkGTaRrD+y/nTcicu+Qpmosvrjh8MTvx5JTbFQlJDcIgSdCc1bY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=h47JoWJB; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="h47JoWJB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 38960C19424; Mon, 17 Nov 2025 13:30:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1763386246; bh=xMhINDDZUPo36kUXPr6r5jMYBQ/OrCLLJKAlTYK573E=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=h47JoWJBOg9JCUY/cOPtysaKsbwDpiJFjUecUP1+JkFWJUIkVWBAqUd3Ko+4ibpqN v6qnWOvB1CSqgAem3YMPL+9yVZqvvpGZpArZtVqETN230DI5DwKtMfoMmY3b4u7TTP 31qO4l6upwd/y2QNfsII+Mm/F0tjXsTsFMq/WQFcHAMJVbW3U2UGmofI2PtuBocG0p s9UVhZ4UYMNCxai2a2CTZ92jiuZIGfhUcRckVg8Pw//S/3HBizwieqPjLmd0Z7iIu1 jVXtLyb7psYrha21NWEosgSeOXVm7v020NTDIc3V5VvrMmsRpGX384HY/ikTyKCyMI fkErY6gp3G7DA== Message-ID: <37bad560-a8f3-4ae2-aa34-1edc635062c0@kernel.org> Date: Mon, 17 Nov 2025 14:30:42 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Linux 6.18-rc6 To: David Wang <00107082@163.com>, Linus Torvalds , catalin.marinas@arm.com, lance.yang@linux.dev, b-padhi@ti.com, akpm@linux-foundation.org Cc: linux-kernel@vger.kernel.org, Jan Polensky References: <20251117082023.90176-1-00107082@163.com> <6c09aaea.aa4a.19a91e379ab.Coremail.00107082@163.com> From: "David Hildenbrand (Red Hat)" Content-Language: en-US In-Reply-To: <6c09aaea.aa4a.19a91e379ab.Coremail.00107082@163.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 17.11.25 13:56, David Wang wrote: > > At 2025-11-17 18:33:58, "Linus Torvalds" wrote: >> On Mon, 17 Nov 2025 at 00:20, David Wang <00107082@163.com> wrote: >>> >>> After upgrade to 6.18-rc6, all my golang programs start to crash, even Go compiler crashes; >>> and when I started bisect, `make vmlinux` crashes too. >> >> Funky funky. Certainly doesn't happen here. >> >>> I am running bisect with 6.18-rc5 now, any chance this has already caught/fixed? >> >> Please do run the bisect (obviously you'll have to build using a >> kernel that works for you), I am not aware of anybody reporting >> anything like this. > > Hi, > > Bisect narrowed it down to > [adfb6609c6809e107ded9a1cd46f519c882e64ea] mm/huge_memory: initialise the tags of the huge zero folio > > It seems happen to program build with older version of go, mine is 1.18.4; and I cannot reproduce it with go1.25.4. > > When I upgraded to 6.18-rc6, go1.18.4 compiler/program would crash with, > > fatal error: arena already initialized > > runtime stack: > runtime.throw({0x9ea9fe?, 0x0?}) > /usr/local/go/src/runtime/panic.go:992 +0x71 fp=0x7ffdf458a248 sp=0x7ffdf458a218 pc=0x435ab1 > runtime.(*mheap).sysAlloc(0xddec20, 0x0?) > /usr/local/go/src/runtime/malloc.go:749 +0x2e9 fp=0x7ffdf458a2e0 sp=0x7ffdf458a248 pc=0x40dee9 > ... > > > And when I `make vmlinux`, I got something like this : > AR vmlinux.a > LD vmlinux.o > GEN .vmlinux.objs > MODPOST vmlinux.symvers > CC .vmlinux.export.o > UPD include/generated/utsversion.h > CC init/version-timestamp.o > KSYMS .tmp_vmlinux0.kallsyms.S > AS .tmp_vmlinux0.kallsyms.o > LD .tmp_vmlinux1 > NM .tmp_vmlinux1.syms > KSYMS .tmp_vmlinux1.kallsyms.S > AS .tmp_vmlinux1.kallsyms.o > .tmp_vmlinux1.kallsyms.S:361542:19: internal compiler error: Aborted > 361542 | .byte 0x00, 0x99, 0xe9 /* T__pfx___x64_sys_inotify_add_watch */ > | ^ > 0x7f983a551def ??? > ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 > 0x7f983a5a695c __pthread_kill_implementation > ./nptl/pthread_kill.c:44 > 0x7f983a551cc1 __GI_raise > ../sysdeps/posix/raise.c:26 > 0x7f983a53a4ab __GI_abort > ./stdlib/abort.c:73 > 0x7f983a53bca7 __libc_start_call_main > ../sysdeps/nptl/libc_start_call_main.h:58 > 0x7f983a53bd64 __libc_start_main_impl > ../csu/libc-start.c:360 > Please submit a full bug report, with preprocessed source (by using -freport-bug). > Please include the complete backtrace with any bug report. > See for instructions. > make[2]: *** [scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1 > make[1]: *** [/home/linan/codes/linux-kernel/linux/Makefile:1242: vmlinux] Error 2 > make: *** [Makefile:248: __sub-make] Error 2 > $ gcc --version > gcc (Debian 14.2.0-19) 14.2.0 > > (It dose not always happens, sometimes I don't get this crash and It dose not always err on same line.) > > And nothing abnormal shows up in kernel message. > > Revert adfb6609c6809e107ded9a1cd46f519c882e64ea can fix my crashing go programs. I just replied privately to a similar report the following: Hi, I observed something similar while testing on Friday between rc4 (good) and rc5+ (bad). I'm sure this it the known issue of adfb6609c6809e107ded9a1cd46f519c882e64ea we discussed already here [1]. @Jan, can you send the fix out today? Otherwise I can take care of this so we get this fixed asap. [1] https://lkml.kernel.org/r/20251109003613.1461433-1-japo@linux.ibm.com -- Cheers David