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: Tue, 21 Nov 2023 10:31:46 +0900 From: Bongsu Jeon <bongsu.jeon@...sung.com> To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Nguyen Dinh Phi <phind.uet@...il.com>, Bongsu Jeon <bongsu.jeon@...sung.com> CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "syzbot+6eb09d75211863f15e3e@...kaller.appspotmail.com" <syzbot+6eb09d75211863f15e3e@...kaller.appspotmail.com> Subject: Re: [PATCH] nfc: virtual_ncidev: Add variable to check if ndev is running On 20/11/2023 19:23, Phi Nguyen wrote: > The issue arises when an skb is added to the send_buff after invoking > ndev->ops->close() but before unregistering the device. In such cases, > the virtual device will generate a copy of skb, but with no consumer > thereafter. Consequently, this object persists indefinitely. > > This problem seems to stem from the existence of time gaps between > ops->close() and the destruction of the workqueue. During this interval, > incoming requests continue to trigger the send function. Dear Krzysztof, Even though i agree on this patch, i think that NFC subsystem could handle this scenario not to trigger the send function after close. Do you think it would be better that each nci driver has the responsibility to handle this scenario? Best regards, Bongsu
Powered by blists - more mailing lists