From: Arjan van de Ven <arjanv@redhat.com>
To: Roberto Fichera <kernel@tekno-soft.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multithreaded coredump patch where?
Date: 17 Dec 2002 13:08:16 +0100 [thread overview]
Message-ID: <1040126896.10390.1.camel@laptop.fenrus.com> (raw)
In-Reply-To: <5.2.0.9.0.20021217105617.00aa31e0@mail.isolaweb.it>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
On Tue, 2002-12-17 at 12:05, Roberto Fichera wrote:
> At 13.21 16/12/02 -0800, mgross wrote:
>
> >I haven't rebased the patches I posted back in June for a while now.
> >
> >Attached is the patch I posted for the 2.4.18 vanilla kernel. Its a bit
> >controversial, but it seems to work for a number of folks. Let me know if
> >you have any troubles re-basing it.
>
> Only one hunk failed on include/asm-ia64/elf.h but fixed by hand.
> Why do you say a bit controversial ?
The design has theoretical (but probably in practice not trivial to
trigger) deadlocks; by design it prevents processes that are sleeping
from running, regardless whether those processes are in kernel space or
not. If they are in kernel space, they can accidentally be holding a
semaphore that something in the core dumping path will need to get (
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-12-17 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 17:28 Roberto Fichera
2002-12-16 21:21 ` mgross
2002-12-17 11:05 ` Roberto Fichera
2002-12-17 12:05 ` Arjan van de Ven
2002-12-17 12:51 ` Roberto Fichera
2002-12-17 12:08 ` Arjan van de Ven [this message]
2002-12-18 16:13 ` mgross
2002-12-19 9:24 ` Roberto Fichera
2002-12-17 12:14 ` Arjan van de Ven
2002-12-18 16:19 ` mgross
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=1040126896.10390.1.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=kernel@tekno-soft.it \
--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®