public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/microcode-ctl/
Date: Tue, 11 Aug 2015 06:34:40 +0000 (UTC)	[thread overview]
Message-ID: <1439274862.719cc5ef240b766953ddbe1e7a6593f8091eed12.vapier@gentoo> (raw)

commit:     719cc5ef240b766953ddbe1e7a6593f8091eed12
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 11 06:28:16 2015 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Tue Aug 11 06:34:22 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=719cc5ef

microcode-ctl: stop installing the init script

Updating microcode on the fly is dangerous as it can modify the set of
valid instructions.  An active example of this is Intel's TSX insns --
the latest microcode push disables the insn on newer CPUs and causes
SIGILL when you try to use it.  But if you test for the insn before the
microcode is updated, it will execute fine.  For daemons that launched
before the update, they'll find the flag works, and then crash later on
when the insn no longer exists.

Thus the only safe way to update microcode is at boot time via a builtin
initramfs.  Details on this operation can be found in #528712#41.

 .../microcode-ctl/microcode-ctl-1.28-r1.ebuild     | 43 ++++++++++++++++++++++
 1 file changed, 43 insertions(+)

diff --git a/sys-apps/microcode-ctl/microcode-ctl-1.28-r1.ebuild b/sys-apps/microcode-ctl/microcode-ctl-1.28-r1.ebuild
new file mode 100644
index 0000000..3aaef2b
--- /dev/null
+++ b/sys-apps/microcode-ctl/microcode-ctl-1.28-r1.ebuild
@@ -0,0 +1,43 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI="5"
+
+inherit toolchain-funcs
+
+MY_P=${PN/-/_}-${PV}
+DESCRIPTION="Intel processor microcode update utility"
+HOMEPAGE="https://fedorahosted.org/microcode_ctl/"
+SRC_URI="https://fedorahosted.org/released/${PN/-/_}/${MY_P}.tar.xz"
+
+LICENSE="GPL-2"
+SLOT="0"
+KEYWORDS="-* ~amd64 ~x86"
+IUSE="selinux"
+
+DEPEND=""
+RDEPEND=">=sys-apps/microcode-data-20090330
+	selinux? ( sec-policy/selinux-cpucontrol )"
+
+S=${WORKDIR}/${MY_P}
+
+src_compile() {
+	emake \
+		CC="$(tc-getCC)" \
+		CFLAGS="${CFLAGS} ${CPPFLAGS} ${LDFLAGS}"
+}
+
+src_install() {
+	dosbin microcode_ctl
+	doman microcode_ctl.8
+	dodoc Changelog README
+}
+
+pkg_preinst() {
+	if has_version "<${CATEGORY}/${PN}-1.28-r1" ; then
+		elog "The init scripts have been removed as they are unsafe.  If you want to update"
+		elog "the microcode in your system, please use an initramfs.  See bug #528712#41 for"
+		elog "details (and bug #557278 for genkernel users)."
+	fi
+}


             reply	other threads:[~2015-08-11  6:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  6:34 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-24 19:45 [gentoo-commits] repo/gentoo:master commit in: sys-apps/microcode-ctl/ Doug Goldstein
2017-07-01 15:12 Sven Wegener
2018-01-01 19:07 Thomas Deutschmann
2018-01-04  9:58 Tobias Klausmann
2018-01-04 10:00 Lars Wendler
2018-01-04 10:00 Lars Wendler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1439274862.719cc5ef240b766953ddbe1e7a6593f8091eed12.vapier@gentoo \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox