| 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: <20071221071728.GL8181@ftp.linux.org.uk> Date: Fri, 21 Dec 2007 07:17:28 +0000 From: Al Viro <viro@....linux.org.uk> To: Srinivas Kommu <kommu@...mail.com> Cc: linux-kernel@...r.kernel.org Subject: Re: driver spin lock and files_lock deadlock question On Thu, Dec 20, 2007 at 10:59:20PM -0800, Srinivas Kommu wrote: > It seems this kind of a deadlock can happen with any kernel lock, not > just files_lock. What's the driver's mistake here? Is it wrong to call > remove_proc_entry() while holding another lock? What is the right thing > to do? remove_proc_entry() is a blocking function... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists