From: Andrew Morton <akpm@digeo.com>
To: Dawson Engler <engler@csl.stanford.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] potential deadlocks
Date: Sun, 2 Mar 2003 22:18:06 -0800 [thread overview]
Message-ID: <20030302221806.59836766.akpm@digeo.com> (raw)
In-Reply-To: <200303030605.h2365oK08706@csl.stanford.edu>
Dawson Engler <engler@csl.stanford.edu> wrote:
>
> BTW, are there known deadlocks (harmless or otherwise)? Debugging
> the checker is a bit hard since false negatives are silent...
Known deadlocks tend to get fixed. But I am surprised that you did not
encounter more of them.
btw, the filesystem transaction operations can be treated as sleeping locks.
So for ext3, journal_start()/journal_stop() may, for lock-ranking purposes,
be treated in the same way as taking and releasing a per-superblock
semaphore. Other filesystems probably have similar restrictions.
Other such "hidden" sleeping locks are lock_sock() and wait_on_inode(). The
latter is rather messy because there is no clear API function which sets
I_LOCK.
And pte_chain_lock() is a custom spinlock.
next prev parent reply other threads:[~2003-03-03 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 3:35 Dawson Engler
2003-03-03 5:25 ` Andrew Morton
2003-03-03 6:05 ` Dawson Engler
2003-03-03 6:18 ` Andrew Morton [this message]
2003-03-03 6:25 ` Dawson Engler
2003-03-03 9:45 ` Nikita Danilov
2003-03-04 7:52 ` Dawson Engler
2003-03-07 11:24 ` Nikita Danilov
2003-03-03 13:56 ` Alan Cox
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=20030302221806.59836766.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=engler@csl.stanford.edu \
--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
all inboxes | Powered by JetHome®