Skip to content

Commit 5d3d5b9

Browse files
taigerhudhowells
authored andcommitted
docs: filesystems: caching/backend-api.rst: fix an object withdrawn API
There's no fscache_are_objects_withdrawn() helper at all to test if cookie withdrawal is completed currently. The cache backend is using fscache_wait_for_objects() to wait all objects to be withdrawn. Signed-off-by: Yue Hu <huyue2@coolpad.com> Signed-off-by: David Howells <dhowells@redhat.com> cc: linux-cachefs@redhat.com Link: https://listman.redhat.com/archives/linux-cachefs/2022-April/006705.html # v1
1 parent c54eead commit 5d3d5b9

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Documentation/filesystems/caching/backend-api.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -110,9 +110,9 @@ to withdraw them, calling::
110110

111111
on the cookie that each object belongs to. This schedules the specified cookie
112112
for withdrawal. This gets offloaded to a workqueue. The cache backend can
113-
test for completion by calling::
113+
wait for completion by calling::
114114

115-
bool fscache_are_objects_withdrawn(struct fscache_cookie *cache);
115+
void fscache_wait_for_objects(struct fscache_cache *cache);
116116

117117
Once all the cookies are withdrawn, a cache backend can withdraw all the
118118
volumes, calling::

0 commit comments

Comments
 (0)