From owner-freebsd-current Tue Apr 22 12:56:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA21221 for current-outgoing; Tue, 22 Apr 1997 12:56:11 -0700 (PDT) Received: from sovcom.relcom.ru (sovcom.relcom.ru [193.125.152.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA21128; Tue, 22 Apr 1997 12:56:03 -0700 (PDT) Received: by sovcom.relcom.ru id AA27700 (5.65.kiae-1 ); Tue, 22 Apr 1997 22:23:53 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 22 Apr 97 22:23:52 +0300 Received: (from ache@localhost) by nagual.ru (8.8.5/8.8.5) id XAA00225; Tue, 22 Apr 1997 23:21:47 +0400 (MSD) Date: Tue, 22 Apr 1997 23:21:45 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Bruce Evans Cc: current@freebsd.org, dyson@freebsd.org Subject: ufs lockstatus bug again (was Re: Recent vfork kernel changes broke csh & tcsh!) In-Reply-To: <199704221843.EAA29497@godzilla.zeta.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 23 Apr 1997, Bruce Evans wrote: > >BTW, this bug easily cause another bug I report early (ufs lockstatus > >panic) when csh or tcsh is login shell. When you call a.sh from login > >shell, sometimes it cause lockstatus panic instead of exiting to getty. > > I haven't seen this. This one line .profile crash 0day-current with 90% probability: exec /usr/local/bin/ssh -c des -e none localhost (assuming you run recent sshd and _not_ explicitly allow des) This line itself not cause crash, crash always happens on the next sync (from update), so you need some little disk activity to see it: page fault in kernel mode: lockstatus+0x8: cmpw $0,0x10(%edx) stack looks like: lockstatus ufs_islocked vfs_msync sync If "exec" in .profile changed to nothing, all work right, i.e. proper error diagnostic printed from ssh and login prompt appearse again. -- Andrey A. Chernov http://www.nagual.ru/~ache/