public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Wang" <00107082@163.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>,
	catalin.marinas@arm.com, david@redhat.com, lance.yang@linux.dev,
	b-padhi@ti.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 6.18-rc6
Date: Mon, 17 Nov 2025 20:56:35 +0800 (CST)	[thread overview]
Message-ID: <6c09aaea.aa4a.19a91e379ab.Coremail.00107082@163.com> (raw)
In-Reply-To: <CAHk-=wikcf_BVAuUZPH3qGGB5TrFZApfDq5B-1LMK8oXCpZ9tg@mail.gmail.com>


At 2025-11-17 18:33:58, "Linus Torvalds" <torvalds@linux-foundation.org> 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 <file:///usr/share/doc/gcc-14/README.Bugs> 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.



FYI
David

  reply	other threads:[~2025-11-17 12:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 22:42 Linux 6.18-rc6 Linus Torvalds
2025-11-17  8:20 ` David Wang
2025-11-17 10:33   ` Linus Torvalds
2025-11-17 12:56     ` David Wang [this message]
2025-11-17 13:30       ` David Hildenbrand (Red Hat)
2025-11-17 13:45         ` David Wang
2025-11-17 14:08           ` David Hildenbrand (Red Hat)
2025-11-17 15:28             ` David Wang
2025-11-17 16:59             ` Xi Ruoyao
2025-11-17 21:19               ` Joan Bruguera Micó
2025-11-17 17:28             ` Linus Torvalds
2025-11-17 17:53               ` David Hildenbrand (Red Hat)
2025-11-17 17:59                 ` Linus Torvalds
2025-11-17 18:24                   ` David Hildenbrand (Red Hat)
2025-11-17 19:17                     ` David Hildenbrand (Red Hat)
2025-11-18  1:10                       ` Linus Torvalds
2025-11-18  4:13                         ` David Wang
2025-11-18 13:55                           ` David Wang
2025-11-18 14:12                             ` David Hildenbrand (Red Hat)
2025-11-18 14:33                               ` David Wang
2025-11-18 14:44                               ` Carlos Llamas
2025-11-18 14:51                                 ` David Hildenbrand (Red Hat)
2025-11-18 14:53                                   ` Carlos Llamas
2025-11-18 15:09                                   ` David Wang
2025-11-18  7:28                         ` David Hildenbrand (Red Hat)
2025-11-18 16:49                           ` Linus Torvalds
2025-11-19 15:42                             ` Catalin Marinas
2025-11-18  3:59             ` Carlos Llamas
2025-11-17 16:42       ` Linus Torvalds
2025-11-17 18:13 ` Guenter Roeck
2025-11-18 17:23 ` Stephanie Gawroriski
2025-11-18 18:01   ` Linus Torvalds
2025-11-18 20:18     ` Stephanie Gawroriski
2025-11-19  9:08       ` Heikki Krogerus
2025-11-19 14:18         ` Stephanie Gawroriski
2025-11-19 15:04         ` Stephanie Gawroriski
2025-11-24  9:50           ` Heikki Krogerus
2025-11-26 16:01             ` Stephanie Gawroriski
2025-11-27  9:53               ` Heikki Krogerus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6c09aaea.aa4a.19a91e379ab.Coremail.00107082@163.com \
    --to=00107082@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=b-padhi@ti.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox