lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 17 Jan 2019 18:01:50 +0800 From: Yafang Shao <laoar.shao@...il.com> To: davem@...emloft.net, edumazet@...gle.com Cc: netdev@...r.kernel.org, shaoyafang@...iglobal.com, Yafang Shao <laoar.shao@...il.com> Subject: [PATCH net-next] net: sock: do not set sk_cookie in sk_clone_lock() The only call site of sk_clone_lock is in inet_csk_clone_lock, and sk_cookie will be set there. So we don't need to set sk_cookie in sk_clone_lock(). That can save an atomic operation. Signed-off-by: Yafang Shao <laoar.shao@...il.com> --- net/core/sock.c | 1 - 1 file changed, 1 deletion(-) diff --git a/net/core/sock.c b/net/core/sock.c index f00902c..21e2a84 100644 --- a/net/core/sock.c +++ b/net/core/sock.c @@ -1726,7 +1726,6 @@ struct sock *sk_clone_lock(const struct sock *sk, const gfp_t priority) newsk->sk_err_soft = 0; newsk->sk_priority = 0; newsk->sk_incoming_cpu = raw_smp_processor_id(); - atomic64_set(&newsk->sk_cookie, 0); if (likely(newsk->sk_net_refcnt)) sock_inuse_add(sock_net(newsk), 1); -- 1.8.3.1
Powered by blists - more mailing lists