Date: Tue, 22 Oct 2024 12:55:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282268] linker_load_module() panics with KASAN during post-panic reboot Message-ID: <bug-282268-227-HYK8QDWzPs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282268-227@https.bugs.freebsd.org/bugzilla/> References: <bug-282268-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282268 --- Comment #2 from Christos Margiolis <christos@freebsd.org> --- Not sure if this theory is correct, but I am noticing that the issue is more frequent when the panic was caused by a manual call to panic(9), as opposed= to, say, a memory issue. I sent you the dump file on Slack because it's too big to attach here. Seems like it's crashing when loading filemon(4): (kgdb) bt #0 __curthread () at /mnt/src/sys/amd64/include/pcpu_aux.h:57 #1 doadump (textdump=3Dtextdump@entry=3D0) at /mnt/src/sys/kern/kern_shutdown.c:404 #2 0xffffffff805a33b6 in db_dump (dummy=3D<optimized out>, dummy2=3D<optim= ized out>, dummy3=3D<optimized out>, dummy4=3D<optimized out>) at /mnt/src/sys/ddb/db_command.c:595 #3 0xffffffff805a31eb in db_command (last_cmdp=3D<optimized out>, cmd_table=3D<optimized out>, dopager=3Dtrue) at /mnt/src/sys/ddb/db_command.c:508 #4 0xffffffff805a2bfd in db_command_loop () at /mnt/src/sys/ddb/db_command.c:555 #5 0xffffffff805a8979 in db_trap (type=3D<optimized out>, code=3D<optimize= d out>) at /mnt/src/sys/ddb/db_main.c:267 #6 0xffffffff81189485 in kdb_trap (type=3D3, code=3Dcode@entry=3D0, tf=3Dtf@entry=3D0xfffffe0046ce0110) at /mnt/src/sys/kern/subr_kdb.c:790 #7 0xffffffff81a201a8 in trap (frame=3D0xfffffe0046ce0110) at /mnt/src/sys/amd64/amd64/trap.c:606 #8 <signal handler called> #9 kdb_enter (why=3D<optimized out>, msg=3D<optimized out>) at /mnt/src/sys/kern/subr_kdb.c:556 #10 0xffffffff810dde37 in vpanic ( fmt=3Dfmt@entry=3D0xffffffff81c8f46f "ASan: Invalid access, %zu-byte %s= at %#lx, %s(%x)", ap=3Dap@entry=3D0xfffffe0046ce03e0) at /mnt/src/sys/kern/kern_shutdown.= c:967 #11 0xffffffff810ddbd5 in panic (fmt=3D0xffffffff81c8f46f "ASan: Invalid ac= cess, %zu-byte %s at %#lx, %s(%x)") at /mnt/src/sys/kern/kern_shutdown.c:892 #12 0xffffffff81160970 in kasan_report (addr=3D18446741875887136624, size= =3D4, write=3Dfalse, pc=3D<optimized out>, code=3D<optimized out>) at /mnt/src/sys/kern/subr_asan.c:202 #13 0xffffffff8107f1f3 in linker_hints_lookup ( path=3D0xffffffff829c65e0 <linker_path> "/boot/kernel;/boot/modules;/boot/dtb;/boot/dtb/overlays", modname=3D0xfffffe004a17ec00 "filemon", modnamelen=3D7, verinfo=3D0x0, pathlen=3D<optimized out>) at /mnt/src/sys/kern/kern_linker.c:2046 #14 linker_search_module (modname=3D0xfffffe004a17ec00 "filemon", modnamele= n=3D7, verinfo=3D0x0) at /mnt/src/sys/kern/kern_linker.c:2134 #15 linker_load_module (kldname=3Dkldname@entry=3D0x0, modname=3D0xfffffe00= 4a17ec00 "filemon", parent=3Dparent@entry=3D0x0, verinfo=3Dverinfo@entry=3D0x0, lfpp=3Dlfpp@entry=3D0xfffffe0046ce0c00) = at /mnt/src/sys/kern/kern_linker.c:2272 #16 0xffffffff81082e23 in kern_kldload (td=3D<optimized out>, file=3Dfile@entry=3D0xfffffe004a17ec00 "filemon", fileid=3Dfileid@entry=3D0xfffffe0046ce0ca0) at /mnt/src/sys/kern/kern_linker.c:1236 #17 0xffffffff81083052 in sys_kldload (td=3D0xffffffff826074b0 <panicstr>, uap=3D<optimized out>) at /mnt/src/sys/kern/kern_linker.c:1259 #18 0xffffffff81a223ae in syscallenter (td=3D0xfffffe005bc4c000) at /mnt/src/sys/amd64/amd64/../../kern/subr_syscall.c:189 #19 amd64_syscall (td=3D0xfffffe005bc4c000, traced=3D0) at /mnt/src/sys/amd64/amd64/trap.c:1192 #20 <signal handler called> #21 0x000012614498a7da in ?? () Backtrace stopped: Cannot access memory at address 0x126142f959a8 (kgdb) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282268-227-HYK8QDWzPs>