linux-kernel - Re: print_vma_addr possible deadlock (was Re: Jeste jeden bug)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c4e36d110802131218i7bcc873bub5c8df96192b9563@mail.gmail.com>
Date:	Wed, 13 Feb 2008 21:18:21 +0100
From:	"Zdenek Kabelac" <zdenek.kabelac@...il.com>
To:	"Jiri Kosina" <jkosina@...e.cz>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Andi Kleen" <ak@...e.de>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: print_vma_addr possible deadlock (was Re: Jeste jeden bug)

2008/2/13, Jiri Kosina <jkosina@...e.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/