From owner-freebsd-net@FreeBSD.ORG  Wed Jun 23 04:45:12 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0CFE216A4CE; Wed, 23 Jun 2004 04:45:12 +0000 (GMT)
Received: from arginine.spc.org (arginine.spc.org [195.206.69.236])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C5AF943D54; Wed, 23 Jun 2004 04:45:11 +0000 (GMT)
	(envelope-from bms@spc.org)
Received: from localhost (localhost [127.0.0.1])
	by arginine.spc.org (Postfix) with ESMTP
	id E2F37651EE; Wed, 23 Jun 2004 05:44:58 +0100 (BST)
Received: from arginine.spc.org ([127.0.0.1])
 by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 76096-08; Wed, 23 Jun 2004 05:44:58 +0100 (BST)
Received: from empiric.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com
	[82.147.17.88])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by arginine.spc.org (Postfix) with ESMTP
	id C8DA4651EB; Wed, 23 Jun 2004 05:44:57 +0100 (BST)
Received: by empiric.dek.spc.org (Postfix, from userid 1001)
	id 1568D614B; Wed, 23 Jun 2004 05:44:57 +0100 (BST)
Date: Wed, 23 Jun 2004 05:44:57 +0100
From: Bruce M Simpson <bms@spc.org>
To: Dan Nelson <dnelson@allantgroup.com>
Message-ID: <20040623044457.GB3838@empiric.dek.spc.org>
Mail-Followup-To: Dan Nelson <dnelson@allantgroup.com>,
	freebsd-net@FreeBSD.org, alfred@FreeBSD.org, kris@FreeBSD.org,
	Jonathan Lennox <lennox@cs.columbia.edu>
References: <20040618114929.GE58783@empiric.dek.spc.org>
	<20040618223507.GA74627@dan.emsphone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040618223507.GA74627@dan.emsphone.com>
cc: Jonathan Lennox <lennox@cs.columbia.edu>
cc: freebsd-net@FreeBSD.org
cc: kris@FreeBSD.org
cc: alfred@FreeBSD.org
Subject: Re: kern/56461: FreeBSD client rpc.lockd incompatible with Linux
	server rpc.lockd
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2004 04:45:12 -0000

On Fri, Jun 18, 2004 at 05:35:07PM -0500, Dan Nelson wrote:
> Linux kernels 2.4.26 and above have fixed this particular bug, so the
> need for a compatibility hack on our end is not as great anymore.

Agreed. I have abandoned work on this for now. If anyone is in desperate
need for this, I can re-jig the patch to work as a sysctl; but this of
course has the caveat that it affects *all* nfs client mounts.

Regards,
BMS