From: Manfred Spraul <manfred@colorfullife.com>
To: Mark Gross <mgross@unix-os.sc.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] multithreaded coredumps for elf exeecutables for O(1) scheduler
Date: Fri, 10 May 2002 19:13:49 +0200 [thread overview]
Message-ID: <3CDBFFCD.94589E4F@colorfullife.com> (raw)
Have you checked that your patch doesn't deadlock on ia64?
> + /* First pause all related threaded processes */
> + if (dump_threads) {
> + suspend_threads();
> + }
> +
> + /* now stop all vm operations */
> + down_write(¤t->mm->mmap_sem);
> + segs = current->mm->map_count;
> +
Stopping all vm operations means that copy_{to,from}_user can cause
deadlocks.
ia64 needs copy_to_user in their stack unwind handler, IIRC called by
ELF_CORE_COPY_REGS.
Afaics you don't handle that. You must dump all thread state before
down_write(mmap_sem). And I don't see how you protect against 2 threads
of one process calling suspend_threads() simultaneously.
--
Manfred
next reply other threads:[~2002-05-10 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 17:13 Manfred Spraul [this message]
2002-05-10 15:13 ` [PATCH] multithreaded coredumps for elf exeecutables for O(1) scheduler Mark Gross
2002-05-13 7:35 ` Vamsi Krishna S.
2002-05-13 14:25 ` Mark Gross
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 13:24 Mark Gross
2002-05-10 19:06 ` Daniel Jacobowitz
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=3CDBFFCD.94589E4F@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@unix-os.sc.intel.com \
/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