linux-kernel - Re: oprofile can cause an NMI to schedule (was: [RT] scheduling and oprofile)

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: <Pine.LNX.4.58.0610240852450.949@gandalf.stny.rr.com>
Date:	Tue, 24 Oct 2006 08:54:42 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	John Levon <levon@...ementarian.org>
cc:	Mike Kravetz <kravetz@...ibm.com>, phil.el@...adoo.fr,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	oprofile-list@...ts.sourceforge.net
Subject: Re: oprofile can cause an NMI to schedule (was: [RT] scheduling and
 oprofile)


On Tue, 24 Oct 2006, John Levon wrote:

> On Mon, Oct 23, 2006 at 10:24:34PM -0400, Steven Rostedt wrote:
>
>
> in_atomic() is supposed to be true in this context, so the test in
> do_page_fault() catches it.
>


	/*
	 * If we're in an interrupt, have no user context or are running in an
	 * atomic region then we must not take the fault..
	 */
	if (in_atomic() || !mm)
		goto bad_area_nosemaphore;


Ahh, missed that one.  So this is an issue that _only_ rt needs to fix.
OK, thanks for pointing that out.

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