From: Al Viro <viro@ftp.linux.org.uk>
To: Srinivas Kommu <kommu@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: driver spin lock and files_lock deadlock question
Date: Fri, 21 Dec 2007 07:17:28 +0000 [thread overview]
Message-ID: <20071221071728.GL8181@ftp.linux.org.uk> (raw)
In-Reply-To: <476B6448.7090805@hotmail.com>
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...
prev parent reply other threads:[~2007-12-21 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 6:59 driver spin lock and files_lock deadlock question Srinivas Kommu
2007-12-21 7:17 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071221071728.GL8181@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=kommu@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox