diff options
| author | Mateusz Guzik <[email protected]> | 2024-08-15 10:33:10 +0200 |
|---|---|---|
| committer | Christian Brauner <[email protected]> | 2024-08-30 08:22:37 +0200 |
| commit | b381fbbccb4cb60aefa1ab7f8e3766ddb4a461db (patch) | |
| tree | 57edc85b86716eceaa8a68045dd2f142221c2f18 /lib/memory-notifier-error-inject.c | |
| parent | 433f9d76a01056dfeaefc15167b11e514e56f956 (diff) | |
vfs: elide smp_mb in iversion handling in the common case
According to bpftrace on these routines most calls result in cmpxchg,
which already provides the same guarantee.
In inode_maybe_inc_iversion elision is possible because even if the
wrong value was read due to now missing smp_mb fence, the issue is going
to correct itself after cmpxchg. If it appears cmpxchg wont be issued,
the fence + reload are there bringing back previous behavior.
Signed-off-by: Mateusz Guzik <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Jeff Layton <[email protected]>
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions