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: <29EC5179-D939-42CD-8577-682BE4B05916@gmail.com> Date: Tue, 03 Sep 2019 14:55:17 -0700 From: "Jonathan Lemon" <jonathan.lemon@...il.com> To: Netdev <netdev@...r.kernel.org> Subject: rtnl_lock() question How appropriate is it to hold the rtnl_lock() across a sleepable memory allocation? On one hand it's just a mutex, but it would seem like it could block quite a few things. -- Jonathan