diff options
| author | Jeff Layton <jlayton@kernel.org> | 2022-08-05 13:42:45 +0300 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2022-08-09 16:13:55 +0300 |
| commit | fb24771faf72a2fd62b3b6287af3c610c3ec9cf1 (patch) | |
| tree | ca92f6258605d877ac7155f86ca95d1e0499f3cd /fs/mbcache.c | |
| parent | 3d7cb6b04c3f3115719235cc6866b10326de34cd (diff) | |
| download | linux-fb24771faf72a2fd62b3b6287af3c610c3ec9cf1.tar.xz | |
fscache: don't leak cookie access refs if invalidation is in progress or failed
It's possible for a request to invalidate a fscache_cookie will come in
while we're already processing an invalidation. If that happens we
currently take an extra access reference that will leak. Only call
__fscache_begin_cookie_access if the FSCACHE_COOKIE_DO_INVALIDATE bit
was previously clear.
Also, ensure that we attempt to clear the bit when the cookie is
"FAILED" and put the reference to avoid an access leak.
Fixes: 85e4ea1049c7 ("fscache: Fix invalidation/lookup race")
Suggested-by: David Howells <dhowells@redhat.com>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'fs/mbcache.c')
0 files changed, 0 insertions, 0 deletions