Re: ext2fs related panic

Can you try this patch ?



Index: ext2_vfsops.c
===================================================================
RCS file: /home/ncvs/src/sys/gnu/ext2fs/ext2_vfsops.c,v
retrieving revision 1.130
diff -u -r1.130 ext2_vfsops.c
--- ext2_vfsops.c	29 Oct 2004 10:42:30 -0000	1.130
+++ ext2_vfsops.c	6 Nov 2004 12:29:20 -0000
_at__at_ -732,6 +732,7 _at__at_
 	ump->um_mountp = mp;
 	ump->um_dev = dev;
 	ump->um_devvp = devvp;
+	ump->um_bo = &devvp->v_bufobj;
 	/* setting those two parameters allowed us to use
 	   ufs_bmap w/o changse !
 	*/

In message <1099742312.809.9.camel_at_taxman>, Stefan Ehmann writes:
>With kernel sources from yesterday I get a panic as soon as I do this:
>
>mount /mnt/stuff
>ls /mnt/stuff
>
>The correspoding line in fstab is this (I haven't checked yet if it also
>happens on rw mounted ext2fs)
>/dev/ad1s1              /mnt/stuff      ext2fs  ro
>
>Unfortunately I had problems when debugging the core with kgdb (maybe
>because it couldn't find symbols for the modules or because I had to
>call doadump by hand).
>
>Anyway, here is a (shortened) transcript from ddb output.
>
>Fatal trap 12: page fault while in kernel mode
>...
>current process = 815 (ls)
>
>trace
>ext2_strategy()
>bufstrategy()
>breadn()
>bread()
>ext2_read()
>ext2_readdir()
>getdirentries()
>Xint0x80_syscall()
>
>I can provide more info if needed.
>
>Thanks
>
>_______________________________________________
>freebsd-current_at_freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.