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: <20231014024321.1002066-2-twuufnxlz@gmail.com> Date: Sat, 14 Oct 2023 10:43:22 +0800 From: Edward AD <twuufnxlz@...il.com> To: horms@...nel.org Cc: davem@...emloft.net, edumazet@...gle.com, johannes.berg@...el.com, johannes@...solutions.net, kuba@...nel.org, linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, syzbot+509238e523e032442b80@...kaller.appspotmail.com, syzkaller-bugs@...glegroups.com, twuufnxlz@...il.com Subject: Re: [PATCH] rfkill: fix deadlock in rfkill_send_events Hi Simon Horman, On Fri, 13 Oct 2023 13:06:38 +0200, Simon Horman wrote: > I am wondering if you considered moving the rfkill_sync() calls > to before &data->mtx is taken, to avoid the need to drop and > retake it? If you move rfkill_sync() before calling &data->mtx, more code will be added because rfkill_sync() is in the loop body. > > Perhaps it doesn't work for some reason (compile tested only!). > But this does seem somehow cleaner for me. BR, edward
Powered by blists - more mailing lists