diff options
author | Oleg Nesterov <oleg@redhat.com> | 2023-11-30 14:56:06 +0300 |
---|---|---|
committer | David Howells <dhowells@redhat.com> | 2023-12-24 18:22:47 +0300 |
commit | 4121b4337146b64560d1e46ebec77196d9287802 (patch) | |
tree | 04cf3050db102dc438e917dcb6859c655e9a9d5f /CREDITS | |
parent | 2daa6404fd2f00985d5bfeb3c161f4630b46b6bf (diff) | |
download | linux-4121b4337146b64560d1e46ebec77196d9287802.tar.xz |
afs: fix the usage of read_seqbegin_or_lock() in afs_lookup_volume_rcu()
David Howells says:
(2) afs_lookup_volume_rcu().
There can be a lot of volumes known by a system. A thousand would
require a 10-step walk and this is drivable by remote operation, so I
think this should probably take a lock on the second pass too.
Make the "seq" counter odd on the 2nd pass, otherwise read_seqbegin_or_lock()
never takes the lock.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
Link: https://lore.kernel.org/r/20231130115606.GA21571@redhat.com/
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions