From owner-freebsd-current  Sun Mar 14 23:51:13 1999
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4B5D8151D3
	for <current@FreeBSD.ORG>; Sun, 14 Mar 1999 23:50:47 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id XAA96296;
	Sun, 14 Mar 1999 23:47:54 -0800 (PST)
	(envelope-from dillon)
Date: Sun, 14 Mar 1999 23:47:54 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199903150747.XAA96296@apollo.backplane.com>
To: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>
Cc: current@FreeBSD.ORG
Subject: Re: Simple DOS against 3.x locks box solid 
References:  <199903142204.BAA03697@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:Matthew Dillon wrote:
:> -			error = acquire(lkp, extflags,
:> -				LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE);
:> +			if (p->p_flag & P_DEADLKTREAT) {
:> +				error = acquire(
:
:This is broken: p may be NULL, it is checked several lines before. 
:My kernel just paniced for this reason.
:
:Well, sorry for late response, but: what was wrong with Tor Egge's 
:"workaround" from kern/8416?
:
:Dima

    We'll get a quick fix committed but the lockmgr stuff needs a real
    going-over... having interrupts using the general lockmgr call is
    a disaster waiting to happen.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message