Re: port-evbmips/50059: evbmips-mips64el panic writing to ext2fs file system

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR port-evbmips/50059; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: port-evbmips/50059: evbmips-mips64el panic writing to ext2fs
 file system
Date: Sat, 18 Jul 2015 19:08:31 +0000

 On Fri, Jul 17, 2015 at 08:45:00PM +0000, jdbaker%mylinuxisp.com@localhost wrote:
  > Beginning around 7.99.15, writing to an ext2fs file system on a Lemote
  > Yeeloong (evbmips-mips64el, LOONGSON) produced system hangs or panics
  > with the following message:
  > 
  > panic: kernel diagnostic assertion "vp->v_type == VREG" failed: file
  > "/x/current/src/sys/ufs/ext2fs/ext2fs_readwrite.c", line 286
  > kernel: breakpoint trap
  > Stopped in pid 16366.1 (cvs) at ffffffff8023d88c:       li      at,0x3
  > db> bt
  > 980000008110f860: 0+ffffffff8023d88c (63061,0,0,ffffffff80668ef0) ra 0 sz 0
  > User-level: pid 16366.1
  > db>
  > 
  > 
  > While the above message was captured during a 'cvs update' operation,
  > it is most readily triggered by extracting a tar archive to a target
  > directory on an ext2fs file system.
 
 some things that would be useful for someone to check:
 
 (1) does this happen on other ports? and if not,
 (2) does this happen using compat_netbsd32 on other ports?
 
 It is far from impossible that someone simply broke ext2fs :-/
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost