From owner-freebsd-current  Sun Sep 20 05:57:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA18642
          for freebsd-current-outgoing; Sun, 20 Sep 1998 05:57:50 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from highwind.com (hurricane.highwind.com [209.61.45.50])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18637
          for <freebsd-current@FreeBSD.ORG>; Sun, 20 Sep 1998 05:57:47 -0700 (PDT)
          (envelope-from info@highwind.com)
Received: (from info@localhost)
	by highwind.com (8.8.6/8.8.6) id IAA06956;
	Sun, 20 Sep 1998 08:56:41 -0400 (EDT)
Date: Sun, 20 Sep 1998 08:56:41 -0400 (EDT)
Message-Id: <199809201256.IAA06956@highwind.com>
From: HighWind Software Information <info@highwind.com>
To: rotel@indigo.ie
CC: tlambert@primenet.com, rotel@indigo.ie, freebsd-current@FreeBSD.ORG,
        jb@cimlogic.com.au
In-reply-to: <199809201129.MAA00530@indigo.ie> (message from Niall Smart on
	Sun, 20 Sep 1998 12:29:14 +0000)
Subject: Re: HighWind products
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


   On Sep 20,  9:26am, Terry Lambert wrote:
   } Subject: Re: HighWind products
   > > } Subject: Re: HighWind products
   > > 
   > > Looks like readdir() is MT safe anyhow.
   > 
   > Only if you use seperate DIR descriptors per thread.

   Yeah, thats a good point, I expect this would be the scenario in
   most programs, but I can think of some where it wouldn't.  It means
   that implementing readdir_r() is as easy as wrapping readdir() with
   a lock though.

We tried that. IT DID NOT WORK. We got all sorts of random memory
corruption with opendir(), lock, readdir(), unlock, closedir().

Perhaps the whole sequence needed to be locked?

-Rob

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message