From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: vxlan: use after free error Date: Mon, 29 May 2017 08:32:47 -0700 Message-ID: <20170529083247.12b1cb60@xeon-e3> References: <03ac7d79-02b7-4bee-d318-9731413bf97b@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Roopa Prabhu , "davem@davemloft.net" , Jiri Benc , pravin shelar , Alexander Duyck , Nicolas Dichtel , "netdev@vger.kernel.org" , Balki Raman To: Mark Bloch Return-path: Received: from mail-pg0-f44.google.com ([74.125.83.44]:34895 "EHLO mail-pg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751128AbdE2Pcu (ORCPT ); Mon, 29 May 2017 11:32:50 -0400 Received: by mail-pg0-f44.google.com with SMTP id 8so24349231pgc.2 for ; Mon, 29 May 2017 08:32:50 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Mon, 29 May 2017 09:28:52 +0300 Mark Bloch wrote: > In my patch I've added the code inside vxlan_sock_release() > after we do: > rcu_assign_pointer(vxlan->vn6_sock, NULL); > rcu_assign_pointer(vxlan->vn4_sock, NULL); Use RCU_INIT_POINTER when assigning NULL. A barrier is not necessary.