From owner-freebsd-stable@FreeBSD.ORG Tue Nov 11 12:51:53 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7E2816A4CE for ; Tue, 11 Nov 2003 12:51:53 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 033D343FBF for ; Tue, 11 Nov 2003 12:51:52 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 1B65D33CC5; Tue, 11 Nov 2003 16:49:44 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 18B6533C85 for ; Tue, 11 Nov 2003 16:49:44 -0400 (AST) Date: Tue, 11 Nov 2003 16:49:44 -0400 (AST) From: "Marc G. Fournier" To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200311112020.hABKKmEg098822@lurza.secnetix.de> Message-ID: <20031111164512.P56037@ganymede.hub.org> References: <200311112020.hABKKmEg098822@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Subject: Re: kernel panic on jailed sshd - 4.9-release X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 20:51:53 -0000 On Tue, 11 Nov 2003, Oliver Fromme wrote: > Kov=E1cs J=E1nos wrote: > > Just installed 4.9-RELEASE with jailed sshd over a null-mounted (bin, > > dev,etc,usr) > > dirs crashing. > > It's well-known that NULLFS (as well as UNIONFS) are unstable > in FreeBSD 4.x and can cause crashes. God, I so hate answers like this ... its the "I'm too lazy to care" answer ... =2E.. and it doesn't even come close to addressing the problem, and that is that in 4.8, he didn't have this problem, while in 4.9, he does ... is there something different in sshd that is causing this? I'm running 4.9-PRERELEASE from Sept 20th, and all my servers have been solid, and sshd is used extensively ... Kovacs, can you back track to a Sept 20th world/kernel to see if the problem persists there? You'll need to use the date=3D option in cvsup to do so ... if that works, try bouncing forward to the 20th of October and see if that exhibits the problem. Basically, I'm curious as to on which date the problem starts, then we can see what got changed in CVS around that date that may have caused this ... it might be something really simple to fix ...