linux-kernel - Re: rtmutex assert failure (was [Patch] restore the RCU callback...)

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:	Tue, 22 Aug 2006 16:20:51 -0700
From:	Bill Huey (hui) <billh@...ppy.monkey.org>
To:	Robert Crocombe <rcrocomb@...il.com>
Cc:	Esben Nielsen <nielsen.esben@...glemail.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>, rostedt@...dmis.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Bill Huey (hui)" <billh@...ppy.monkey.org>
Subject: Re: rtmutex assert failure (was [Patch] restore the RCU callback...)

On Mon, Aug 21, 2006 at 06:37:22PM -0700, Bill Huey wrote:
> I'll come up with a patch tomorrow to try and get a clean stack trace. I've
> made some change to the bug dump output to make it more preemption aware,
> but, as you can, some tweeking is needed.

I turned off the tracing in the latency tracking stuff and a relatively
small patch is here against -rt8:

	http://mmlinux.sourceforge.net/public/against-2.6.17-rt8-0.diff

This might help with the stack trace. The stack trace being kind of clobbered is a
different issue entirely. I don't know since I can't replicate your problem over here.
I'm going to start looking over the rt mutex more carefully and see what case might
make this assert trigger. I'll try and deal with this one and a time.

I'm new at this bug fixing thing so give me a bit of time. Apparently Ingo's on
long vacation.

bill

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