From: Manfred Spraul <manfred@colorfullife.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: deadlock in crashed multithreaded job
Date: Tue, 02 Oct 2001 15:46:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805291@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805288@msgid-missing>
Erich Focht wrote:
>
> The question that remains is how to deal with nested locks on the same
> resource that can lead to deadlocks. Is there any (un)written rule that
> one should avoid them in the Linux Kernel? Or are there any approaches to
> deal with them (which are not yet included in the Kernel)?
>
Yes, semaphores and spinlocks are not recursive. There is one exception
for rw spinlocks, they can recurse on read. I'm not aware that there are
any plans to change that.
My patch avoids calling copy_from_user in elf_core_dump, Andrea adds a
limited recursion support and uses that to prevent the deadlock.
With his patch you can recurse on on down_read() if you pass special
parameters.
But full recursion support is not planned.
--
Manfred
prev parent reply other threads:[~2001-10-02 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 9:16 [Linux-ia64] Re: deadlock in crashed multithreaded job Erich Focht
2001-10-02 15:46 ` Manfred Spraul [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=marc-linux-ia64-105590698805291@msgid-missing \
--to=manfred@colorfullife.com \
--cc=linux-ia64@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