linux-kernel - Re: [PATCH] perf_counter: Provide functions for locking and pinning the context for a task

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: <20090601231428.GF749@elte.hu>
Date:	Tue, 2 Jun 2009 01:14:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf_counter: Provide functions for locking and
	pinning the context for a task


* Paul Mackerras <paulus@...ba.org> wrote:

> Ingo Molnar writes:
> 
> > -tip testing found that these patches are causing a crash:
> 
> Argh.  What was userspace doing at the time of the crash, do you 
> know? It looks like it might have been on/off-lining a cpu, 
> judging by the stack trace.  Would there have been any counters 
> attached to the task doing there, or were there any per-cpu 
> counters active?

Yeah, indeed that box has a CPU hotplug testcase - sets cpu1 to 
offline then online.

There should be no counters active anywhere during that.

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