From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Jiri Kosina" <jkosina@suse.cz>
Cc: "Ingo Molnar" <mingo@elte.hu>, "Andi Kleen" <ak@suse.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: print_vma_addr possible deadlock (was Re: Jeste jeden bug)
Date: Wed, 13 Feb 2008 21:18:21 +0100 [thread overview]
Message-ID: <c4e36d110802131218i7bcc873bub5c8df96192b9563@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802132039240.30955@jikos.suse.cz>
2008/2/13, Jiri Kosina <jkosina@suse.cz>:
> On Wed, 13 Feb 2008, Ingo Molnar wrote:
>
> > The longer-term fix will be to not run int3 exception handlers in a
> > non-preemptible context (like 32-bit does) - but that will need more
> > testing.
>
> Yup, exactly.
>
> > Jiri Kosina reported the following deadlock scenario with
> > show_unhandled_signals enabled:
>
> Actually the kernel error message was reported to me by Zdenek. Zdenek,
> could you please try the fix?
Ok - great I do not get this BUG log
So this has fixed 2 problems a 3 other remains :)
I'll open them tomorrow I guess :) at my two were fixed pretty quickly.
PS: Ingo did you have a chance to check my kernel IPI problem ?
Zdenek
next prev parent reply other threads:[~2008-02-13 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c4e36d110802130841l591f20a4j32759821543b554c@mail.gmail.com>
2008-02-13 16:52 ` Jeste jeden bug Jiri Kosina
2008-02-13 16:58 ` print_vma_addr possible deadlock (was Re: Jeste jeden bug) Jiri Kosina
2008-02-13 17:13 ` Andi Kleen
2008-02-13 19:35 ` Ingo Molnar
2008-02-13 19:40 ` Jiri Kosina
2008-02-13 20:18 ` Zdenek Kabelac [this message]
2008-02-13 22:09 ` Andi Kleen
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=c4e36d110802131218i7bcc873bub5c8df96192b9563@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=ak@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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