Date: Fri, 13 Sep 2019 19:55:50 +0200 From: Harry Schmalzbauer <freebsd@omnilan.de> To: freebsd-stable <freebsd-stable@freebsd.org> Subject: 12.1-prerelease nullfs? related panic Message-ID: <8e8956fb-d892-5eb7-de95-a05b00ce9007@omnilan.de>
next in thread | raw e-mail | index | archive | help
Hello, got this panic today booting a test machine with kernel from 09/09/2019, r352054: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80541088 stack pointer = 0x28:0xfffffe0000578420 frame pointer = 0x28:0xfffffe0000578470 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 593 (limits) trap number = 9 panic: general protection fault cpuid = 0 time = 1568392101 KDB: stack backtrace: #0 0xffffffff8061eec7 at kdb_backtrace+0x67 #1 0xffffffff805d323d at vpanic+0x19d #2 0xffffffff805d3093 at panic+0x43 #3 0xffffffff80941d2c at trap_fatal+0x39c #4 0xffffffff8094113c at trap+0x6c #5 0xffffffff8091b4ac at calltrap+0x8 #6 0xffffffff805421c2 at null_lookup+0x162 #7 0xffffffff809c40c0 at VOP_LOOKUP_APV+0x50 #8 0xffffffff806948f1 at lookup+0x6d1 #9 0xffffffff80693dc7 at namei+0x437 #10 0xffffffff806aaad2 at kern_statat+0x72 #11 0xffffffff806ab2cf at sys_fstatat+0x2f #12 0xffffffff809428e4 at amd64_syscall+0x364 #13 0xffffffff8091bdd0 at fast_syscall_common+0x101 Uptime: 26s #4 0xffffffff80941d2c in trap_fatal (frame=<value optimized out>, eva=<value optimized out>) at /usr/local/share/deploy-tools/RELENG_12/src/sys/amd64/amd64/trap.c:943 #5 0xffffffff8094113c in trap (frame=0xfffffe0000578360) at RELENG_12/src/sys/amd64/include/counter.h:87 #6 0xffffffff8091b4ac in calltrap () at /usr/local/share/deploy-tools/RELENG_12/src/sys/amd64/amd64/exception.S:289 #7 0xffffffff80541088 in null_nodeget (mp=0xfffff8000524d000, lowervp=0xfffff8000535b000, vpp=0xfffffe00005784a8) at /usr/local/share/deploy-tools/RELENG_12/src/sys/fs/nullfs/null_subr.c:117 #8 0xffffffff805421c2 in null_lookup (ap=0xfffffe0000578568) at /usr/local/share/deploy-tools/RELENG_12/src/sys/fs/nullfs/null_vnops.c:429 #9 0xffffffff809c40c0 in VOP_LOOKUP_APV (vop=0xffffffff80c81d98, a=0xfffffe0000578568) at vnode_if.c:126 #10 0xffffffff806948f1 in lookup (ndp=0xfffffe0000578768) at vnode_if.h:54 #11 0xffffffff80693dc7 in namei (ndp=0xfffffe0000578768) at /usr/local/share/deploy-tools/RELENG_12/src/sys/kern/vfs_lookup.c:445 #12 0xffffffff806aaad2 in kern_statat (td=0xfffff800052ad5e0, flag=<value optimized out>, fd=<value optimized out>, path=0x8002600b0 <Address 0x8002600b0 out of bounds>, pathseg=UIO_USERSPACE, sbp=0xfffffe0000578888, hook=0) at /usr/local/share/deploy-tools/RELENG_12/src/sys/kern/vfs_syscalls.c:2300 #13 0xffffffff806ab2cf in sys_fstatat (td=<value optimized out>, uap=0xfffff800052ad9a0) at /usr/local/share/deploy-tools/RELENG_12/src/sys/kern/vfs_syscalls.c:2277 #14 0xffffffff809428e4 in amd64_syscall (td=0xfffff800052ad5e0, traced=0) at RELENG_12/src/sys/amd64/amd64/../../kern/subr_syscall.c:135 This occured only once and after the reboot, I found a corrupted file on my nullfs-mount. It wasn't mutilated, but showed content of another valid file in the same directory (like 'cat fil1 >> vfile2') Any ideas if this has been recently addressed since 09/09? Thanks, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8e8956fb-d892-5eb7-de95-a05b00ce9007>