From owner-freebsd-current Tue Apr 8 13:10:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA28061 for current-outgoing; Tue, 8 Apr 1997 13:10:46 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA28054 for ; Tue, 8 Apr 1997 13:10:44 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.159]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id NAA01919 for ; Tue, 8 Apr 1997 13:10:41 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.5/8.7.3) id PAA00267; Tue, 8 Apr 1997 15:08:25 -0500 (CDT) Message-ID: <19970408150825.38520@peeper.my.domain> Date: Tue, 8 Apr 1997 15:08:25 -0500 From: Tom Jackson To: FreeBSD-current Subject: Re: new ufs exec crash in -current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69e In-Reply-To: ; from ????????????? on Tue, Apr 08, 1997 at 04:43:23PM +0400 Reply-To: toj@gorilla.net Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Apr 08, 1997 at 04:43:23PM +0400, ????????????? wrote: > > Put this line in your .login and you got system crash withing a minute > after this command executed: > > exec /usr/local/bin/ssh -l -e none -c des locahlost > ^^^^^ this cipher must be _not_ > supported, it is true, > if you run sshd 1.2.18 > > If you remove "exec" word from here, you'll just get proper error > diagnostic about not supported cipher, but no crash. > > Crash details: > page fault in kernel mode > > stack looks like: > > lockstatus > ufs_islocked > vfs_msync > sync > vfs_update > kproc_start > main > > Please, fix. > > I've got 3 of these fatal trap 12 pagefaults in the last 2 days; I'm not running ssh. Usually happens when su'ing to root and such. -- Tom Jackson I'm ProChoice->FreeBSD toj@gorilla.net http://www.freebsd.org tjackson@tulsix.utulsa.edu "Out in the Ozone Again"