diff options
author | Oleg Nesterov <[email protected]> | 2023-11-30 12:56:17 +0100 |
---|---|---|
committer | David Howells <[email protected]> | 2023-12-24 15:22:48 +0000 |
commit | df91b9dfdee23072641570b1efc049f19d839ae8 (patch) | |
tree | dcfa69ea62242d637ff7bf8b5fd32c00127a3af7 /scripts/generate_rust_analyzer.py | |
parent | 1702e0654ca9a7bcd7c7619c8a5004db58945b71 (diff) |
afs: use read_seqbegin() in afs_check_validity() and afs_getattr()
David Howells says:
(3) afs_check_validity().
(4) afs_getattr().
These are both pretty short, so your solution is probably good for them.
That said, afs_vnode_commit_status() can spend a long time under the
write lock - and pretty much every file RPC op returns a status update.
Change these functions to use read_seqbegin(). This simplifies the code
and doesn't change the current behaviour, the "seq" counter is always even
so read_seqbegin_or_lock() can never take the lock.
Signed-off-by: Oleg Nesterov <[email protected]>
Signed-off-by: David Howells <[email protected]>
cc: Marc Dionne <[email protected]>
cc: [email protected]
Link: https://lore.kernel.org/r/[email protected]/
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions