linux-kernel - Re: [git pull] tracing fixes

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.58.0807182118260.4932@gandalf.stny.rr.com>
Date:	Fri, 18 Jul 2008 21:18:45 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [git pull] tracing fixes



On Fri, 18 Jul 2008, Ingo Molnar wrote:
> ok, figured it out today: the lockups were due to the NMI watchdog and a
> missing NMI protection in cpu_clock(). I've reactivated the topic that
> solves this problem area and it all works fine now.
>
> the sched.o change probably made a difference just because it reduced
> the cross section between the NMI watchdog and the scheduler, making
> lockups less likely during the ftrace self-test. I'll revert it once the
> tracing/nmisafe is upstream.

Ingo,

Thanks a lot for looking into this.

-- Steve

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