[Bug 281524] msdosfs error over USB causes a kernel panic
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 17 Sep 2024 23:32:29 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281524
Xin LI <delphij@FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Closed |Open
CC| |delphij@FreeBSD.org
Resolution|Unable to Reproduce |---
--- Comment #6 from Xin LI <delphij@FreeBSD.org> ---
I think it's reasonable to expect that the system to not panic (at least, not
to panic with a NULL pointer deference) when hardware fails, in this particular
case it appears that fsync() decided to give up, but it did not done so
gracefully (and should), I think this is suggesting that there was a bug that
should be fixed:
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 00 06 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT asc:27,0 (Write protected)
(da0:umass-sim0:0:0:0): Info: 0
(da0:umass-sim0:0:0:0): Error 13, Unretryable error
g_vfs_done():da0s1[WRITE(offset=2560, length=512)]error = 13
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 00 06 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT asc:27,0 (Write protected)
(da0:umass-sim0:0:0:0): Info: 0
(da0:umass-sim0:0:0:0): Error 13, Unretryable error
g_vfs_done():da0s1[WRITE(offset=2560, length=512)]error = 13
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 00 06 00 00 01 00
(da0:umass-sim0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0): SCSI sense: DATA PROTECT asc:27,0 (Write protected)
(da0:umass-sim0:0:0:0): Info: 0
(da0:umass-sim0:0:0:0): Error 13, Unretryable error
g_vfs_done():da0s1[WRITE(offset=2560, length=512)]error = 13
fsync: giving up on dirty (error = 13) 0xfffff80246d73e00: type VCHR state
VSTATE_CONSTRUCTED op 0xffffffff818abe28
usecount 1, writecount 0, refcount 8 seqc users 0 rdev 0xfffff80006679000
hold count flags ()
flags ()
v_object 0xfffff800210e9840 ref 0 pages 5 cleanbuf 5 dirtybuf 1
lock type mntfs: EXCL by thread 0xfffff802183f5000 (pid 2401, umount, tid
102536)
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x1000102a4
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80a75445
stack pointer = 0x28:0xfffffe016bd30a20
frame pointer = 0x28:0xfffffe016bd30a40
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 = 2401 (umount)
rdi: fffff80246d73ee0 rsi: fffffe0017e2dbe0 rdx: 0000000000000000
rcx: ffffffffffffffe0 r8: fffffe000fe19420 r9: 0000000000000005
rax: 0000000100010204 rbx: fffffe0017e2dbe0 rbp: fffffe016bd30a40
r10: 0000000000000005 r11: fffff800038cb000 r12: 00000000a00010a4
r13: 0000000000000000 r14: fffff80246d73e00 r15: 0000000000000000
trap number = 12
panic: page fault
cpuid = 3
time = 1726433998
KDB: stack backtrace:
#0 0xffffffff80b7fefd at kdb_backtrace+0x5d
#1 0xffffffff80b32bd1 at vpanic+0x131
#2 0xffffffff80b32a93 at panic+0x43
#3 0xffffffff8100091b at trap_fatal+0x40b
#4 0xffffffff81000966 at trap_pfault+0x46
#5 0xffffffff80fd6d48 at calltrap+0x8
#6 0xffffffff80bedfda at bufwrite+0x1da
#7 0xffffffff80c310b0 at vn_fsync_buf+0x230
#8 0xffffffff80bee16b at bufsync+0x3b
#9 0xffffffff80c14e7f at bufobj_invalbuf+0x19f
#10 0xffffffff80c17e9e at vgonel+0x26e
#11 0xffffffff80c183b1 at vgone+0x31
#12 0xffffffff809c370e at mntfs_freevp+0xe
#13 0xffffffff809ca05e at msdosfs_unmount+0x1de
#14 0xffffffff80c0cb67 at dounmount+0x787
#15 0xffffffff80c0c375 at kern_unmount+0x2f5
#16 0xffffffff810011c0 at amd64_syscall+0x100
#17 0xffffffff80fd765b at fast_syscall_common+0xf8
Uptime: 37m28s
Dumping 880 out of 14229 MB:..2%..11%..22%..31%..42%..51%..62%..71%..82%..91%
--
You are receiving this mail because:
You are the assignee for the bug.