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: Mon, 25 May 2020 12:40:29 +0200 From: Markus Elfring <Markus.Elfring@....de> To: Zhang Qiang <qiang.zhang@...driver.com>, Tejun Heo <tj@...nel.org>, Lai Jiangshan <jiangshanlai@...il.com> Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org Subject: Re: [v2] workqueue: Fix double kfree for rescuer > I see, kfree does nothing with null pointers and direct return. > but again kfree is not a good suggestion. I have got the impression that the implementation detail is important here if non-null pointers (according to valid rescuer objects) are occasionally passed by the corresponding data structure member for the callback function “rcu_free_wq”. Can another clarification attempt reduce unwanted confusion for this patch review? Regards, Markus
Powered by blists - more mailing lists