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
| ||
|
Message-ID: <5c506c95-1f18-9f6b-efd1-50e0f6d097da@linux.alibaba.com> Date: Thu, 13 Jan 2022 23:15:11 +0800 From: Wen Gu <guwen@...ux.alibaba.com> To: Karsten Graul <kgraul@...ux.ibm.com>, davem@...emloft.net, kuba@...nel.org Cc: linux-s390@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH net] net/smc: Avoid setting clcsock options after clcsock released On 2022/1/12 5:38 pm, Karsten Graul wrote: > On 11/01/2022 17:34, Wen Gu wrote: >> Thanks for your reply. >> >> On 2022/1/11 6:03 pm, Karsten Graul wrote: >>> On 10/01/2022 10:38, Wen Gu wrote: >>>> We encountered a crash in smc_setsockopt() and it is caused by >>>> accessing smc->clcsock after clcsock was released. >>>> >>> >>> In the switch() the function smc_switch_to_fallback() might be called which also >>> accesses smc->clcsock without further checking. This should also be protected then? >>> Also from all callers of smc_switch_to_fallback() ? >>> > > Lets go with your initial patch (improved to address the access in smc_switch_to_fallback()) > for now because it solves your current problem. > Since the upcoming v2 patch added clcsock check in smc_switch_to_fallback(), the original subject is inappropriate. So I sent a new patch named 'net/smc: Transitional solution for clcsock race issue' instead of a v2. Thanks, Wen Gu
Powered by blists - more mailing lists