From owner-freebsd-bugs@FreeBSD.ORG  Wed Jun 23 04:40:03 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A19EC16A4CE; Wed, 23 Jun 2004 04:40:03 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7DF0F43D39; Wed, 23 Jun 2004 04:40:03 +0000 (GMT)
	(envelope-from bms@FreeBSD.org)
Received: from freefall.freebsd.org (bms@localhost [127.0.0.1])
	i5N4e36m072123;	Wed, 23 Jun 2004 04:40:03 GMT
	(envelope-from bms@freefall.freebsd.org)
Received: (from bms@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5N4e30m072119;
	Wed, 23 Jun 2004 04:40:03 GMT
	(envelope-from bms)
Date: Wed, 23 Jun 2004 04:40:03 GMT
From: Bruce M Simpson <bms@FreeBSD.org>
Message-Id: <200406230440.i5N4e30m072119@freefall.freebsd.org>
To: lennox@cs.columbia.edu, bms@FreeBSD.org, bms@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: kern/56461: FreeBSD client rpc.lockd incompatible with Linux
	server rpc.lockd
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2004 04:40:03 -0000

Synopsis: FreeBSD client rpc.lockd incompatible with Linux server rpc.lockd

State-Changed-From-To: analyzed->suspended
State-Changed-By: bms
State-Changed-When: Wed Jun 23 04:39:05 GMT 2004
State-Changed-Why: 
Problem fixed in Linux now but will take time to filter down to
each distro (disparate userland and kernel components responsible
for the issue). Therefore a workaround in FreeBSD probably isn't
warranted.


Responsible-Changed-From-To: bms->freebsd-bugs
Responsible-Changed-By: bms
Responsible-Changed-When: Wed Jun 23 04:39:05 GMT 2004
Responsible-Changed-Why: 
Back to the free pool

http://www.freebsd.org/cgi/query-pr.cgi?pr=56461