diff options
author | 2022-07-06 12:40:31 -0400 | |
---|---|---|
committer | 2022-07-06 12:40:31 -0400 | |
commit | 6e180327153071281dbbf6a16759e49862debdca (patch) | |
tree | bb089c228824d356fc5387e601444a178812a8f3 /net/unix/af_unix.c | |
parent | switch try_to_unlazy_next() to __legitimize_mnt() (diff) | |
download | wireguard-linux-6e180327153071281dbbf6a16759e49862debdca.tar.xz wireguard-linux-6e180327153071281dbbf6a16759e49862debdca.zip |
namei: move clearing LOOKUP_RCU towards rcu_read_unlock()
try_to_unlazy()/try_to_unlazy_next() drop LOOKUP_RCU in the
very beginning and do rcu_read_unlock() only at the very end.
However, nothing done in between even looks at the flag in
question; might as well clear it at the same time we unlock.
Note that try_to_unlazy_next() used to call legitimize_mnt(),
which might drop/regain rcu_read_lock() in some cases. This
is no longer true, so we really have rcu_read_lock() held
all along until the end.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions