Subject: kern/14504: Latest filesystem code can cause a kernel panic
To: None <gnats-bugs@gnats.netbsd.org>
From: Matthias Scheler <tron@colwyn.zhadum.de>
List: netbsd-bugs
Date: 11/08/2001 17:50:55
>Number:         14504
>Category:       kern
>Synopsis:       Latest filesystem code can cause a kernel panic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 08 08:51:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.5Y 2001-10-08 sources
>Organization:
Matthias Scheler                                  http://scheler.de/~matthias/
>Environment:
System: NetBSD lyssa.zhadum.de 1.5Y NetBSD 1.5Y (LYSSA) #2: Thu Nov 8 17:25:14 CET 2001 tron@lyssa.zhadum.de:/src/sys/compile/LYSSA i386
Architecture: i386
Machine: i386

>Description:
My system paniced twiced with the lastest filesystem code during heavy
disk activity. Here is a traceback:

uvm_fault(0xc03a46e0, 0x0, 0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 eip c0303046 cs 8 eflags 10216 cr2 0 cpl c000ff64
panic: trap
Begin traceback...
trap() at trap+0x1ea
--- trap (number 6) ---
memcpy(c59d2160,ffffffff,7ffff,0) at memcpy+0x1a
biodone(c59d2160,10,11,19000,0) at biodone+0x52
ufs_strategy(d3e91cc4,a12a,d3e91ddc,c017bea3,0) at ufs_strategy+0xe5
VOP_STRATEGY(c59d2160,d4890ca4,0,c08df8bc) at VOP_STRATEGY+0x2b
bwrite(c59d2160,11,d3e91d5c,c01789c9,d3e91d40) at bwrite+0xdf
vn_bwrite(d3e91d44,0,d3e92004,c0178897,d3e91d58) at vn_bwrite+0x14
VOP_BWRITE(c59d2160,11,d3e91dac,c0256fa0,d4890ca4) at VOP_BWRITE+0x2b
bawrite(c59d2160,11,0,0) at bawrite+0x1a
ffs_full_fsync(d3e91e58,d4890ca4,c0932000,c0253472,0) at ffs_full_fsync+0x137
ffs_fsync(d3e91e58,10012,d3e91e7c,c02571bb,d4890ca4) at ffs_fsync+0x3c
VOP_FSYNC(d4890ca4,c0854f00,0,0,0,0,0,d3e92004) at VOP_FSYNC+0x58
ffs_sync(c091ea00,3,c0854f00,d3e92004) at ffs_sync+0xcf
sync_fsync(d3e91f28,0,d3e91f2c,c017a997,ffffffff) at sync_fsync+0x5c
VOP_FSYNC(d47c1bf4,c0854f00,8,0,0,0,0,d3e92004) at VOP_FSYNC+0x58
sched_sync(d3e92004) at sched_sync+0xb1
End traceback...
syncing disks...

>How-To-Repeat:
Cause heavy filesystem activity on a system with the a kernel using the
lastest FFS code. I used this command:

find * -user root | xargs rm

>Fix:
None provide.
>Release-Note:
>Audit-Trail:
>Unformatted: