Bug
1733097 [wpt PR 30909] - FSA: Make removal of files compatible with file locking, a=testonly
Automatic update from web-platform-tests
FSA: Make removal of files compatible with file locking
Removing a file requires acquiring a write lock at the URL.
The lock is released once the operation completes.
remove() requires acquiring an exclusive lock at the URL.
For the sake of backwards compatibility, removeEntry() only requires
acquiring a shared lock. This means that you cannot remove a file with
an open access handle, but you CAN remove a file with open writables.
Removal of directories is not yet compatible with file locking.
Bug:
1114923,
1254078
Change-Id: I1eee08deaff9508e3c90d78ae35b2c181bb18122
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/
3174315
Commit-Queue: Austin Sullivan <asully@chromium.org>
Auto-Submit: Austin Sullivan <asully@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/main@{#926938}
--
wpt-commits:
2a49a9e6e4cfadbc32eebdc8be0c14e72e0b77cf
wpt-pr: 30909