From owner-freebsd-bugs  Sat Jul  5 13:30:04 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA19070
          for bugs-outgoing; Sat, 5 Jul 1997 13:30:04 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA19062;
          Sat, 5 Jul 1997 13:30:02 -0700 (PDT)
Date: Sat, 5 Jul 1997 13:30:02 -0700 (PDT)
Message-Id: <199707052030.NAA19062@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Bill Fenner <fenner@parc.xerox.com>
Subject: Re: kern/3384: telldir-seekdir can cause livelock
Reply-To: Bill Fenner <fenner@parc.xerox.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3384; it has been noted by GNATS.

From: Bill Fenner <fenner@parc.xerox.com>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: kern/3384: telldir-seekdir can cause livelock
Date: Sat, 5 Jul 1997 13:05:24 PDT

 Actually, the relevant portion of the seekdir man page is probably
 
 			 It is safe to use a previous telldir() val-
      ue immediately after a call to opendir() and before any calls to
      readdir().
 
 which is what the test program does, so either the man page or the
 implementation is wrong.
 
 The readdir() man page doesn't happen to mention that the storage that
 readdir() returns will be freed when you call closedir(); this is not
 the case on other systems so should perhaps be documented (especially
 since it's the cause of one of the bugs in the test program).
 
   Bill