From owner-freebsd-stable@FreeBSD.ORG  Wed Feb 15 15:04:22 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@FreeBSD.org
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 94A8316A420
	for <stable@FreeBSD.org>; Wed, 15 Feb 2006 15:04:22 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 94FDA43D58
	for <stable@FreeBSD.org>; Wed, 15 Feb 2006 15:04:21 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id A347546C19;
	Wed, 15 Feb 2006 10:03:56 -0500 (EST)
Date: Wed, 15 Feb 2006 15:07:21 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Jun Kuriyama <kuriyama@imgsrc.co.jp>
In-Reply-To: <7mvevg1ykw.wl%kuriyama@imgsrc.co.jp>
Message-ID: <20060215150623.E57748@fledge.watson.org>
References: <7mvevg1ykw.wl%kuriyama@imgsrc.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: stable@FreeBSD.org
Subject: Re: rpc.lockd brokenness
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2006 15:04:22 -0000


On Wed, 15 Feb 2006, Jun Kuriyama wrote:

> - Problem is uninterruptible lock?  Or other problem exists?

BTW, the kernel->user protocol for rpc.lockd on the client currently cannot 
support lock request aborts, so the sleep waiting on locks has to remain 
uninterruptible until that is fixed.

Robert N M Watson