netdev - Re: [net-next] vxlan: use a more suitable function when assigning NULL

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20170607.152632.1622878385522436454.davem@davemloft.net>
Date:   Wed, 07 Jun 2017 15:26:32 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     markb@...lanox.com
Cc:     jbenc@...hat.com, stephen@...workplumber.org,
        netdev@...r.kernel.org
Subject: Re: [net-next] vxlan: use a more suitable function when assigning
 NULL

From: Mark Bloch <markb@...lanox.com>
Date: Wed,  7 Jun 2017 14:36:58 +0300

> When stopping the vxlan interface we detach it from the socket.
> Use RCU_INIT_POINTER() and not rcu_assign_pointer() to do so.
> 
> Suggested-by: Stephen Hemminger <stephen@...workplumber.org>
> Signed-off-by: Mark Bloch <markb@...lanox.com>

Applied, thanks Mark.