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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 30 May 2020 12:40:42 +0200 From: Markus Elfring <Markus.Elfring@....de> To: Jia He <justin.he@....com>, kvm@...r.kernel.org, netdev@...r.kernel.org, virtualization@...ts.linux-foundation.org Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Kaly Xin <Kaly.Xin@....com>, Stefan Hajnoczi <stefanha@...hat.com>, Stefano Garzarella <sgarzare@...hat.com> Subject: Re: [PATCH v3] virtio_vsock: Fix race condition in virtio_transport_recv_pkt() > This fixes it by checking sk->sk_shutdown(suggested by Stefano) after > lock_sock since sk->sk_shutdown is set to SHUTDOWN_MASK under the > protection of lock_sock_nested. How do you think about a wording variant like the following? Thus check the data structure member “sk_shutdown” (suggested by Stefano) after a call of the function “lock_sock” since this field is set to “SHUTDOWN_MASK” under the protection of “lock_sock_nested”. Would you like to add the tag “Fixes” to the commit message? Regards, Markus
Powered by blists - more mailing lists