Messages in this thread |  | | | Date | Fri, 21 Dec 2007 07:17:28 +0000 | | From | Al Viro <> | | 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...
|  |