getDirectoryContents:readDirStream: invalid argument (Invalid argument) about unix HOT 6 CLOSED

$ git grep "getDirectoryContents "
Cabal/Distribution/PackageDescription/Check.hs:      getDirectoryContents = System.Directory.getDirectoryContents . relative,
Cabal/Distribution/PackageDescription/Check.hs:    getDirectoryContents :: FilePath -> m [FilePath],
Cabal/Distribution/PackageDescription/Check.hs:      files <- getDirectoryContents ops dir
Cabal/Distribution/Simple/GHC/Internal.hs:        objss <- mapM getDirectoryContents dirs
Cabal/Distribution/Simple/LHC.hs:        objss <- mapM getDirectoryContents dirs
Cabal/Distribution/Simple/Test.hs:    getDirectoryContents testLogDir
Cabal/Distribution/Simple/UHC.hs:          mapM (\ d -> getDirectoryContents d >>= filterM (isPkgDir (display compilerid) d))
Cabal/Distribution/Simple/Utils.hs:      (files, dirs') <- collect [] [] =<< getDirectoryContents (topdir </> dir)
Cabal/Distribution/Simple/Utils.hs:    files <- getDirectoryContents (dir </> dir')
Cabal/Distribution/Simple/Utils.hs: = do files <- getDirectoryContents dir
Cabal/Distribution/Simple/Utils.hs:    files <- getDirectoryContents dir

On OS X 10.10 Yosemite, if you have a directory that can be returned
in a single getdirentries64 call (for example, a directory with one file),
and you read from the directory at EOF twice, you get EOF both times:
        fd = open("dir")
        getdirentries64(fd) returns data
        getdirentries64(fd) returns 0 (EOF)
        getdirentries64(fd) returns 0 (EOF)

But if you remove the file in the middle between the two calls, the
second call returns an error instead.
        fd = open("dir")
        getdirentries64(fd) returns data
        getdirentries64(fd) returns 0 (EOF)
        remove("dir/file")
        getdirentries64(fd) returns ENOENT/EINVAL

Whether you get ENOENT or EINVAL depends on exactly what was
in the directory. It is deterministic, just data-dependent.

This only happens in small directories. A directory containing more data
than fits in a 4k getdirentries64 call will return EOF correctly.
(It's not clear if the criteria is that the directory be split across multiple
getdirentries64 calls or that it be split across multiple file system blocks.)

$ gcc readdirbug.c 
$ ./a.out 
mkdir /tmp/readdirbug
create /tmp/readdirbug/file1

opendir /tmp/readdirbug
readdir: found .
readdir: found ..
readdir: found file1
readdir: EOF
readdir: EOF
readdir: EOF
closedir

opendir /tmp/readdirbug
readdir: found .
readdir: found ..
readdir: found file1
readdir: EOF
rm /tmp/readdirbug/file1
readdir: EOF
readdir: EOF
closedir
ok - everything worked