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]

Message-ID: <e6babb600608231024u3b5462d2oecc940f670516405@mail.gmail.com>
Date:	Wed, 23 Aug 2006 10:24:24 -0700
From:	"Robert Crocombe" <rcrocomb@...il.com>
To:	"hui Bill Huey" <billh@...ppy.monkey.org>
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>
Subject: Re: rtmutex assert failure (was [Patch] restore the RCU callback...)

On 8/23/06, Robert Crocombe <rcrocomb@...il.com> wrote:
> On 8/22/06, hui Bill Huey <billh@...ppy.monkey.org> wrote:
> > 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
>
> I'm going to assume that the #error here:
>
> +#ifdef CONFIG_LATENCY_TRACE
> +#error
> +       stop_trace();
> +#endif
>
> is to see if I'm awake.  No, but gcc is.  I just removed it (?).

Just in case it was a "hey, dummy, don't do that" kind of thing, I
built another kernel with latency tracing off, but the end result is
the same.

-- 
Robert Crocombe
rcrocomb@...il.com
-
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/