From: Pavel Machek <pavel@suse.cz>
To: "Vamsi Krishna S ." <vamsi@in.ibm.com>
Cc: "Gross, Mark" <mark.gross@intel.com>,
"'Erich Focht'" <efocht@ess.nec.de>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org,
"'Bharata B Rao'" <bharata@in.ibm.com>
Subject: Re: PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel.
Date: Wed, 15 May 2002 14:04:48 +0000 [thread overview]
Message-ID: <20020515140448.C37@toy.ucw.cz> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C057B485B@orsmsx111.jf.intel.com> <20020515120722.A17644@in.ibm.com>
Hi!
> To respond to your specific question, if a thread happens to be in
> kernel mode when some other thread is dumping core (capturing
> register state of other threads, to be more accurate) then
> we would capture the _user mode_ register of that thread from the
> bottom of it's kernel stack. GDB will show back trace untill the
> thread entered kernel (int 0x80), eip will be pointing to the
> instruction after the system call (return address).
Okay, what about:
Thread 1 is in kernel and holds lock A. You need lock A to dump state.
When you move 1 to phantom runqueue, you loose ability to get A and
deadlock.
What prevents that?
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-05-15 20:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 16:38 PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel Gross, Mark
2002-05-15 6:37 ` Vamsi Krishna S .
2002-05-15 14:04 ` Pavel Machek [this message]
2002-05-15 20:53 ` Mark Gross
2002-05-16 10:11 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 15:44 Gross, Mark
2002-05-17 12:26 Erich Focht
[not found] <59885C5E3098D511AD690002A5072D3C057B485B@orsmsx111.jf.intel.com.suse.lists.linux.kernel>
[not found] ` <20020515120722.A17644@in.ibm.com.suse.lists.linux.kernel>
[not found] ` <20020515140448.C37@toy.ucw.cz.suse.lists.linux.kernel>
[not found] ` <200205152353.g4FNrew30146@unix-os.sc.intel.com.suse.lists.linux.kernel>
2002-05-16 12:54 ` Andi Kleen
2002-05-16 14:13 ` Mark Gross
2002-05-16 17:27 ` Andi Kleen
2002-05-16 17:36 ` Daniel Jacobowitz
2002-05-16 18:08 ` Mark Gross
2002-05-16 21:32 ` Alan Cox
2002-05-16 21:24 ` Robert Love
2002-05-16 18:40 ` Mark Gross
2002-05-13 19:17 Mark Gross
2002-05-14 15:35 ` Erich Focht
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=20020515140448.C37@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=bharata@in.ibm.com \
--cc=efocht@ess.nec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=torvalds@transmeta.com \
--cc=vamsi@in.ibm.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