From owner-freebsd-current Tue Mar 10 05:43:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22796 for freebsd-current-outgoing; Tue, 10 Mar 1998 05:43:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA22782 for ; Tue, 10 Mar 1998 05:42:56 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-22-b-149.dialup.umn.edu by mhub3.tc.umn.edu; Tue, 10 Mar 98 07:42:50 -0600 Date: Tue, 10 Mar 1998 07:39:49 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: current@FreeBSD.ORG Subject: ext2_sync and NULL inode and VNON v_type Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In current as of 980310, a r/w mounted ext2 filesystem panics on the first sync. This happens when a vnode of type VNON with ip == NULL is processed. I have added a test for a v_type of VNON in ext2_sync(). if (VOP_ISLOCKED(vp)) continue; + if ( vp->v_type == VNON ) + continue; ip = VTOI(vp); if (ip == NULL) { I haven't yet tried writing to the mounted file system with this patch. dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message