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: <20190308.112814.595862977917502151.davem@davemloft.net>
Date:   Fri, 08 Mar 2019 11:28:14 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     sbrivio@...hat.com
Cc:     jishi@...hat.com, sd@...asysnail.net, tom@...bertland.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net] vxlan: Fix GRO cells race condition between
 receive and link delete

From: Stefano Brivio <sbrivio@...hat.com>
Date: Fri,  8 Mar 2019 16:40:57 +0100

> If we receive a packet while deleting a VXLAN device, there's a chance
> vxlan_rcv() is called at the same time as vxlan_dellink(). This is fine,
> except that vxlan_dellink() should never ever touch stuff that's still in
> use, such as the GRO cells list.
> 
> Otherwise, vxlan_rcv() crashes while queueing packets via
> gro_cells_receive().
> 
> Move the gro_cells_destroy() to vxlan_uninit(), which runs after the RCU
> grace period is elapsed and nothing needs the gro_cells anymore.
> 
> This is now done in the same way as commit 8e816df87997 ("geneve: Use GRO
> cells infrastructure.") originally implemented for GENEVE.
> 
> Reported-by: Jianlin Shi <jishi@...hat.com>
> Fixes: 58ce31cca1ff ("vxlan: GRO support at tunnel layer")
> Signed-off-by: Stefano Brivio <sbrivio@...hat.com>
> Reviewed-by: Sabrina Dubroca <sd@...asysnail.net>

Applied and queued up for -stable, thank you.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ