linux-kernel - Re: System deadlock on 2.6.24-rt20 (-rt27 panics on locking-api-selftests)

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 5 Apr 2009 20:39:11 +0200
From:	Remy Bohmer <linux@...mer.net>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: System deadlock on 2.6.24-rt20 (-rt27 panics on 
	locking-api-selftests)

Hello Thomas,

>> I integrated -rt27, but this one fails on the locking api-selftests.
>> Is this a bug in the selftest? Or is there a real locking bug behind
>> it?
>
> Don't think so. The rw locks fixups which we did between -rt20 and
> -rt27 might have screwed the lockdep selftests where we create
> deadlock situations.

This is what I hoped for ;-)  (A bug in the testtooling...)

> What happens if you disable the self tests ?

The system boots and seems to run properly. We did not yet test for a
longer period of time, but the first looks are that the hangups we had
are gone now. But it would be good for the peace of mind if the
locking-selftest was working properly.

Thanks.

Kind Regards,

Remy
--
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/