Re: kern/41189: kernel panic xen dom0 using mke2fs & WAPBL

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

The following reply was made to PR kern/41189; it has been noted by GNATS.

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost,
        jdwhite%iastate.edu@localhost, tsutsui%ceres.dti.ne.jp@localhost
Subject: Re: kern/41189: kernel panic xen dom0 using mke2fs & WAPBL
Date: Sun, 13 Sep 2009 21:30:50 +0900

 It looks there are two different problems.
 
 >> Another panic.  This time I was unmounting an ext2 filesystem, so the 
 >> problem isn't with mke2fs, but seemingly with ext2 filesystems in 
 >> general.
 >>
 >>  panic: kernel diagnostic assertion "LIST_EMPTY(&vp->v_dirtyblkhd)" 
 >> failed: file "/home/builds/ab/netbsd-5/src/sys/kern/vfs_subr.c", line 872
 
 This one seems the same problem as PR kern/39914,
 and this can't be reproducible on -current for me.
 
 >> Running 'mke2fs -v -I 128 /dev/sd0m':
 >> 
 >> panic: kernel diagnostic assertion "rw_lock_held(&wl->wl_rwlock)" 
 
 This one is the "block device node on wapbl" problem mentioned in
 the release note, and -current still has this problem:
 
 http://www.NetBSD.org/releases/formal-5/NetBSD-5.0.html#errata
 >> Using block device nodes directly for I/O may cause a kernel crash
 >> when the file system containing /dev is FFS and is mounted with -o log.
 >> Workaround: use raw disk devices, or remount the file system without -o log.
 (I wonder if there is other PR about this errata)
 
 ---
 Izumi Tsutsui