diff options
author | David Howells <dhowells@redhat.com> | 2024-12-16 23:41:01 +0300 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2024-12-21 00:34:04 +0300 |
commit | 6e0b503dc65c89b83fbfafb4dac5201c844da1de (patch) | |
tree | 8e0a2178b2319c17bc1bb7237a98a6d11c492958 /tools/perf/scripts/python/task-analyzer.py | |
parent | 627cf645277b6f8e6128e2c86907a81970bce87a (diff) | |
download | linux-6e0b503dc65c89b83fbfafb4dac5201c844da1de.tar.xz |
afs: Don't use mutex for I/O operation lock
Don't use the standard mutex for the I/O operation lock, but rather
implement our own as the standard mutex must be released in the same thread
as locked it. This is a problem when it comes to doing async FetchData
where the lock will be dropped from the workqueue that processed the
incoming data and not from the issuing thread.
Signed-off-by: David Howells <dhowells@redhat.com>
Link: https://lore.kernel.org/r/20241216204124.3752367-12-dhowells@redhat.com
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions