From 387d2e671c597a51b4166667a16e740a8e1449fa Mon Sep 17 00:00:00 2001 From: Dana Robinson Date: Mon, 16 Sep 2019 15:17:31 -0700 Subject: Added a release note for HDFFV-10892 (fcntl lock bug). --- release_docs/RELEASE.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt index f26d969..7c09c2b 100644 --- a/release_docs/RELEASE.txt +++ b/release_docs/RELEASE.txt @@ -538,6 +538,28 @@ Bug Fixes since HDF5-1.10.3 release (JTH - 2018/08/25, HDFFV-10501) + - fcntl(2)-based file locking incorrectly passed the lock argument struct + instead of a pointer to the struct, causing errors on systems where + flock(2) is not available. + + File locking is used when files are opened to enforce SWMR semantics. A + lock operation takes place on all file opens unless the + HDF5_USE_FILE_LOCKING environment variable is set to the string "FALSE". + flock(2) is preferentially used, with fcntl(2) locks as a backup if + flock(2) is unavailable on a system (if neither is available, the lock + operation fails). On these systems, the file lock will often fail, which + causes HDF5 to not open the file and report an error. + + This bug only affects POSIX systems. Win32 builds on Windows use a no-op + locking call which always succeeds. Systems which exhibit this bug will + have H5_HAVE_FCNTL defined but not H5_HAVE_FLOCK in the configure output. + + This bug affects HDF5 1.10.0 through 1.10.5. + + fcntl(2)-based file locking now correctly passes the struct pointer. + + (DER - 2019/08/27, HDFFV-10892) + Java Library: ---------------- -- cgit v0.12