diff options
| author | Larry Knox <lrknox@hdfgroup.org> | 2022-02-12 04:34:16 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-02-12 04:34:16 (GMT) |
| commit | 97b8fad8edbfa4c4c482a0b43f86885914c19fa5 (patch) | |
| tree | 0fe20e4c381c83fee35bba97aad537886a67677d /release_docs | |
| parent | 96cf19499b540d8fe5547690b85d18b45f4c4b85 (diff) | |
| download | hdf5-97b8fad8edbfa4c4c482a0b43f86885914c19fa5.zip hdf5-97b8fad8edbfa4c4c482a0b43f86885914c19fa5.tar.gz hdf5-97b8fad8edbfa4c4c482a0b43f86885914c19fa5.tar.bz2 | |
Revert "Fix metadata cache bug when resizing a pinned/protected entry (#1358)" (#1437)
This reverts commit 01092658a3095c31d7dc1ed1beebbd965095c244.
Diffstat (limited to 'release_docs')
| -rw-r--r-- | release_docs/RELEASE.txt | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt index 56b5e42..f68a7fe 100644 --- a/release_docs/RELEASE.txt +++ b/release_docs/RELEASE.txt @@ -1082,23 +1082,6 @@ Bug Fixes since HDF5-1.12.0 release =================================== Library ------- - - Fixed a metadata cache bug when resizing a pinned/protected cache entry - - When resizing a pinned/protected cache entry, the metadata - cache code previously would wait until after resizing the - entry to attempt to log the newly-dirtied entry. This would - cause H5C_resize_entry to mark the entry as dirty and make - H5AC_resize_entry think that it doesn't need to add the - newly-dirtied entry to the dirty entries skiplist. - - Thus, a subsequent H5AC__log_moved_entry would think it - needs to allocate a new entry for insertion into the dirty - entry skip list, since the entry doesn't exist on that list. - This causes an assertion failure, as the code to allocate a - new entry assumes that the entry is not dirty. - - (JTH - 2022/01/12) - - Fixed an H5Pget_filter_by_id1/2() assert w/ out of range filter IDs Both H5Pget_filter_by_id1 and 2 did not range check the filter ID, which |