linux-kernel - Re: BITS handling of CPU microcode updates

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: <m2ipv8kx8y.fsf@firstfloor.org>
Date:	Thu, 24 Mar 2011 14:46:21 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Burt Triplett <burt@...triplett.org>, linux-kernel@...r.kernel.org
Subject: Re: BITS handling of CPU microcode updates

Henrique de Moraes Holschuh <hmh@....eng.br> writes:
>
> Very well, I will send patches to fix that behaviour, as well as some
> other stuff I noticed that was not updated to match the recommended
> actions documented by the SDM and some Intel application notes.

I don't think you can easily -- there's no kernel interface
to distingush the "explicit user action" case from automatic loading.

This all would need a new kernel interface.

I suppose all the test labs have learned by now how to disable
automatic updates ...

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/