linux-kernel - Re: Warning during suspend with MS-7310 mainboard

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200907310837.23487.rusty@rustcorp.com.au>
Date:	Fri, 31 Jul 2009 08:37:22 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Dave Jones <davej@...hat.com>
Cc:	"Langsdorf, Mark" <mark.langsdorf@....com>,
	Eric Sesterhenn <eric.sesterhenn@...xperts.de>,
	linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org
Subject: Re: Warning during suspend with MS-7310 mainboard

On Fri, 31 Jul 2009 02:16:29 am Dave Jones wrote:
> On Thu, Jul 30, 2009 at 11:38:22AM -0500, Langsdorf, Mark wrote:
>  > I'll look into it.
>  > 
>  > First time I've had this bug reported, though.
>  > 
> 
> It's happening because the suspend code runs with interrupts disabled,
> and the powerpc workaround we do in the cpufreq suspend hook
> calls the drivers ->get method.
> 
> powernow-k8's ->get does an smp_call_function_single
> which needs interrupts enabled

Yeah, I was confused: my patch changed set_cpus_allowed_ptr() to
an smp_call_function.  If the latter is a bad idea with irqs disabled, the
former certainly was...

Thanks,
Rusty.
--
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/