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, 23 Oct 2018 12:40:21 -0700 From: Tejun Heo <tj@...nel.org> To: "Theodore Y. Ts'o" <tytso@....edu> Cc: syzbot <syzbot+a50c7541a4a55cd49b02@...kaller.appspotmail.com>, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com, linux-fsdevel@...r.kernel.org, jiangshanlai@...il.com Subject: Re: possible deadlock in flush_workqueue (2) Hello, On Tue, Oct 23, 2018 at 10:28:04AM -0400, Theodore Y. Ts'o wrote: > The other, and I think better way, we could fix this is to have an > alternate destroy_never_used_workqueue() function which skips the > drain_workqueue(). Yeah, I'm okay with this approach. Maybe name it destroy_workqueue_skip_drain()? Thanks. -- tejun
Powered by blists - more mailing lists