mirror of
https://github.com/HDFGroup/hdf5.git
synced 2025-01-30 15:32:37 +08:00
Merge pull request #1924 in HDFFV/hdf5 from ~DEROBINS/hdf5_der:develop_minor_pr to develop
* commit '387d2e671c597a51b4166667a16e740a8e1449fa': Added a release note for HDFFV-10892 (fcntl lock bug).
This commit is contained in:
commit
046e6e8770
@ -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:
|
||||
----------------
|
||||
|
Loading…
Reference in New Issue
Block a user