From: Erich Focht <focht@ess.nec.de>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: deadlock in crashed multithreaded job
Date: Tue, 02 Oct 2001 09:16:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805288@msgid-missing> (raw)
On Mon, 1 Oct 2001, Manfred Spraul wrote:
> > The symptoms: running the tests (make check) sometimes ends up
> > with hanging processes.
>
> Does it _only_ hang during coredumping, or also during normal usage?
>
> Could you remove
> down_read(&mmap_sem);
> binfmt->coredump();
> up_read(&mmap_sem);
> from fs/exec.c and rerun your tests?
Setting the coredumpsize limit to 0 already solves the problem.
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)?
> The hang during coredumping is known, there are 2 fixes [I have one, not
> yet released, Andrea wrote one, IIRC included in his -aa kernels].
Do these solutions deal only with the coredump problem or with nested
critical sections?
Thanks,
Erich
next reply other threads:[~2001-10-02 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 9:16 Erich Focht [this message]
2001-10-02 15:46 ` [Linux-ia64] Re: deadlock in crashed multithreaded job Manfred Spraul
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-105590698805288@msgid-missing \
--to=focht@ess.nec.de \
--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