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]

Message-ID: <alpine.LFD.2.00.0904051257470.747@localhost.localdomain>
Date:	Sun, 5 Apr 2009 13:00:49 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Remy Bohmer <linux@...mer.net>
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)

On Fri, 3 Apr 2009, Remy Bohmer wrote:

> Hello Thomas,
> 
> 2009/4/3 Remy Bohmer <linux@...mer.net>:
> > Hello Thomas,
> >
> >>> Does anybody recognise these backtraces? And if so, is there a fix for
> >>> it already?
> >>
> >> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.24.7-rt27.bz2
> 
> 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. What happens if you disable the self tests ?

Thanks,

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