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

[Jason White <jdwhite%iastate.edu@localhost>]

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

From: Jason White <jdwhite%iastate.edu@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost
Subject: Re: kern/41189: kernel panic xen dom0 using mke2fs & WAPBL
Date: Fri, 17 Apr 2009 16:59:34 -0500

 > On Apr 17,  8:37pm, ad%netbsd.org@localhost (Andrew Doran) wrote:
 > -- Subject: Re: kern/41189: kernel panic xen dom0 using mke2fs & WAPBL
 >
 > | It was my understanding that no ext2fs file systems are involved, other
 > | than the one being created with mke2fs. Have I misread the PR?
 >
 > You are right, the second panic was my fault as I mentioned in the PR
 > from unmounting ext2fs.
 
   The machine I've been testing on has three ext2 partitions on it.  In 
 the course of narrowing down what triggers this bug and testing patches,
 I'd successfully made three ext2 filesystems (when / (sd0a) was mounted 
 without 'log') on different partitions -- none of which was ever ffs 
 formatted.
 
 Typically I've been running mke2fs on just one of the ext2 partitions, 
 but I was in a situation where I had booted with log enabled on / and 
 had mounted one of the other ext2 partitions.  When finished, I 
 unmounted it and (to my surprise) caused a kernel panic.  Up until that 
 time I'd only been running mke2fs to trigger the panic.