From owner-freebsd-fs@FreeBSD.ORG  Wed Oct  8 15:25:20 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1D1DA7F8;
 Wed,  8 Oct 2014 15:25:20 +0000 (UTC)
Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu
 [IPv6:2001:470:8b2d:1e1c:21b:21ff:feb8:d7b0])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "khavrinen.csail.mit.edu", Issuer "Client CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id CE303E6D;
 Wed,  8 Oct 2014 15:25:19 +0000 (UTC)
Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1])
 by khavrinen.csail.mit.edu (8.14.7/8.14.7) with ESMTP id s98FPIBs012951
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256
 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA);
 Wed, 8 Oct 2014 11:25:18 -0400 (EDT)
 (envelope-from wollman@khavrinen.csail.mit.edu)
Received: (from wollman@localhost)
 by khavrinen.csail.mit.edu (8.14.7/8.14.7/Submit) id s98FPHhm012948;
 Wed, 8 Oct 2014 11:25:17 -0400 (EDT) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21557.22365.961980.709081@khavrinen.csail.mit.edu>
Date: Wed, 8 Oct 2014 11:25:17 -0400
From: Garrett Wollman <wollman@csail.mit.edu>
To: Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: 9.3 NFS client bug?
In-Reply-To: <1402889337.60119616.1412731241078.JavaMail.root@uoguelph.ca>
References: <21556.24590.269326.188103@khavrinen.csail.mit.edu>
 <1402889337.60119616.1412731241078.JavaMail.root@uoguelph.ca>
X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (khavrinen.csail.mit.edu [127.0.0.1]); Wed, 08 Oct 2014 11:25:18 -0400 (EDT)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Oct 2014 15:25:20 -0000

<<On Tue, 7 Oct 2014 21:20:41 -0400 (EDT), Rick Macklem <rmacklem@uoguelph.ca> said:

> As far as I know, this has never worked correctly for FreeBSD. The
> unlink() invalidates the directory offset cookies and then it has
> trouble finding the next entry.
> To make the above loop work correctly for FreeBSD, it needs to be
> re-written to start at the beginning of the directory after each
> unlink().

How about instead we fix FreeBSD to work properly?  Clearly it is not
impossible since the Linux NFS client does work.  What exactly is the
issue?  (Forgive me, I know very little about how VOP_READDIR works
under the hood.)

-GAWollman