public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 894eaf5184dda4f851b01d2ed6806d0b0609b321
Date: Tue, 11 Jun 2019 18:08:55 +0100	[thread overview]
Message-ID: <20190611170856.2FB0E84FDC0@people01.i.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  894eaf5184dda4f851b01d2ed6806d0b0609b321 (commit)
      from  8e101c0bdaea04dc759773342d719b8daeb95f67 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 894eaf5184dda4f851b01d2ed6806d0b0609b321
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Jun 11 17:07:23 2019 +0000

    smt: Only disable SMT when the kernel thinks it is vulnerable
    
    On virtual machines, it does not make sense to disable SMT for the
    virtual cores. This has to be done by the hypervisor.
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 src/initscripts/system/smt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/src/initscripts/system/smt b/src/initscripts/system/smt
index f85f567fa..f83776c1a 100644
--- a/src/initscripts/system/smt
+++ b/src/initscripts/system/smt
@@ -23,7 +23,7 @@ case "${1}" in
 		# Disable SMT when the processor is vulnerable to Foreshadow or Fallout/ZombieLoad/RIDL
 		for vuln in l1tf mds; do
 			if [ -r "/sys/devices/system/cpu/vulnerabilities/${vuln}" ] && \
-					[ "$(</sys/devices/system/cpu/vulnerabilities/${vuln})" != "Not affected" ]; then
+					[[ "$(</sys/devices/system/cpu/vulnerabilities/${vuln})" =~ "SMT vulnerable" ]]; then
 				# Disable SMT
 				boot_mesg "Disabling Simultaneous Multi-Threading (SMT)..."
 				echo "forceoff" > /sys/devices/system/cpu/smt/control


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2019-06-11 17:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190611170856.2FB0E84FDC0@people01.i.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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