linux-kernel - Re: [PATCH 2/2] i7300

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: <4900A5CA.5070107@linux.intel.com>
Date:	Thu, 23 Oct 2008 18:26:50 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	paulmck@...ux.vnet.ibm.com
CC:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	Len Brown <lenb@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Henroid, Andrew D" <andrew.d.henroid@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 2/2] i7300_idle driver v1.55


> Suppose that one of the idle CPUs takes an interrupt, whose handler
> accesses the module being removed.  How is this handled?

We're just talking about idle notifier code here. Interrupts shouldn't
ever call idle notifiers directly.

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