linux-kernel - Re: sleeping function called from invalid context at kernel/mutex.c

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

Message-ID: <b647ffbd0810020659j2e5d38c2v51847000de682492@mail.gmail.com>
Date:	Thu, 2 Oct 2008 16:59:07 +0300
From:	"Dmitry Adamushko" <dmitry.adamushko@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Peter Oruba" <peter.oruba@....com>,
	"Sitsofe Wheeler" <sitsofe@...oo.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: sleeping function called from invalid context at kernel/mutex.c

[ cc'd: lkml ]

On 02/10/2008, Dmitry Adamushko <dmitry.adamushko@...il.com> wrote:
> On 02/10/2008, Ingo Molnar <mingo@...e.hu> wrote:
>  >
>  >  * Peter Oruba <peter.oruba@....com> wrote:
>  >
>  >  > microcode_update_cpu() is still there, being called from
>  >  > microcode_init_cpu() and mc_sysdev_resume().
>  >
>  >
>  > ah, microcode_update_cpu, not update_microcode_cpu. So yes, the problem
>  >  is still there with the latest code.
>

Right, I've been looking at the wrong tree. Please find the fix
enclosed. Compiles ok, shouldn't break anything else.

 >
 >         Ingo
 >



-- 
Best regards,
Dmitry Adamushko
--
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/