afs: fix the usage of read_seqbegin_or_lock()
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | afs: fix the usage of read_seqbegin_or_lock() in afs_lookup_volume_rcu()fs/ | +2 | 0 replies | |
| 2/3 | afs: fix the usage of read_seqbegin_or_lock() in afs_find_server*()fs/ | +4 | 0 replies | |
| 3/3 | afs: use read_seqbegin() in afs_check_validity() and afs_getattr()fs/ | +6 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] afs: fix the usage of read_seqbegin_or_lock()
Hello,
Every usage of read_seqbegin_or_lock() in fs/afs is wrong, the counter is always even so read_seqbegin_or_lock() can never take the lock.
The users should either make it odd on the 2nd pass, or use read_seqbegin() instead.
Oleg.
---
fs/afs/callback.c | 3 ++- fs/afs/inode.c | 15 ++++++--------- fs/afs/server.c | 7 ++++--- 3 files changed, 12 insertions(+), 13 deletions(-)