From owner-freebsd-current Thu Jan 31 13:55:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 1848537B404 for ; Thu, 31 Jan 2002 13:55:54 -0800 (PST) Received: (qmail 26689 invoked by uid 0); 31 Jan 2002 21:55:52 -0000 Received: from pd90032d6.dip.t-dialin.net (HELO gmx.net) (217.0.50.214) by mail.gmx.net (mp008-rz3) with SMTP; 31 Jan 2002 21:55:52 -0000 Message-ID: <3C59BD73.2000403@gmx.net> Date: Thu, 31 Jan 2002 22:56:03 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-current@freebsd.org Subject: Re: panic in vfs_syscalls References: <3C59A6CD.6090102@gmx.net> <20020131125519.F18604@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Michael Nottebrock [020131 12:19] wrote: > >>I'm getting these kind of panics with yesterday's kernel every time I >>try to use rpm. >> > > Thanks, I'm pretty sure I know what the fix is, but won't be able > to take a shot until later tonight, for now you can just remove > all FILEDESC_LOCK/UNLOCK calls from chroot_refuse_vdir_fds and > that should keep you panic free. It does indeed. Thanks! -- Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message