Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #191012

Re: CVE-2017-5754 - ETA?

From Vincent Lefevre <vincent@vinc17.net>
Newsgroups linux.debian.user
Subject Re: CVE-2017-5754 - ETA?
Date 2018-01-12 22:50 +0100
Message-ID <v7fn3-5cJ-1@gated-at.bofh.it> (permalink)
References (1 earlier) <v4kCC-2bg-11@gated-at.bofh.it> <v77IS-lC-3@gated-at.bofh.it> <v797Y-1md-17@gated-at.bofh.it> <v7eKl-4Yc-11@gated-at.bofh.it> <v7f3H-54I-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 2018-01-12 21:21:06 +0000, Nick wrote:
> It might have aged out of the buffer that dmesg reports on.

No, there's the beginning of the dmesg output:

[    0.000000] Linux version 4.9.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04)

But I think I've found the reason:

In arch/x86/mm/kaiser.c:

void __init kaiser_check_boottime_disable(void)
{
[...]
        if (boot_cpu_has(X86_FEATURE_XENPV))
                goto silent_disable;
[...]
disable:
        pr_info("disabled\n");

silent_disable:
        kaiser_enabled = 0;
        setup_clear_cpu_cap(X86_FEATURE_KAISER);
}

I must be in the "silent_disable" case (this is a Xen guest).

It's unfortunate that no-one mentions this case!

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

CVE-2017-5754 - ETA? francis picabia <fpicabia@gmail.com> - 2018-01-04 15:00 +0100
  Re: CVE-2017-5754 - ETA? Don Armstrong <don@debian.org> - 2018-01-04 21:50 +0100
    Re: CVE-2017-5754 - ETA? francis picabia <fpicabia@gmail.com> - 2018-01-08 16:40 +0100
      Re: CVE-2017-5754 - ETA? Jeroen Mathon <jeroenmathonmac@gmail.com> - 2018-01-08 17:20 +0100
      Re: CVE-2017-5754 - ETA? Tixy <tixy@yxit.co.uk> - 2018-01-08 18:10 +0100
        Re: CVE-2017-5754 - ETA? Sven Joachim <svenjoac@gmx.de> - 2018-01-08 18:40 +0100
      Re: CVE-2017-5754 - ETA? Richard Hector <richard@walnut.gen.nz> - 2018-01-08 22:30 +0100
        Re: CVE-2017-5754 - ETA? francis picabia <fpicabia@gmail.com> - 2018-01-10 13:50 +0100
    Re: CVE-2017-5754 - ETA? Vincent Lefevre <vincent@vinc17.net> - 2018-01-12 14:40 +0100
      Re: CVE-2017-5754 - ETA? bw <bwtnguy@yahoo.com> - 2018-01-12 16:10 +0100
        Re: CVE-2017-5754 - ETA? Jack Dangler <tdldev@gmail.com> - 2018-01-12 17:00 +0100
          Re: CVE-2017-5754 - ETA? Roberto C. Sánchez <roberto@debian.org> - 2018-01-12 17:00 +0100
        Re: CVE-2017-5754 - ETA? Vincent Lefevre <vincent@vinc17.net> - 2018-01-12 22:10 +0100
          Re: CVE-2017-5754 - ETA? Roberto C. Sánchez <roberto@debian.org> - 2018-01-12 22:20 +0100
            Re: CVE-2017-5754 - ETA? Vincent Lefevre <vincent@vinc17.net> - 2018-01-12 22:20 +0100
          Re: CVE-2017-5754 - ETA? Nick <debuser@acrasis.net> - 2018-01-12 22:30 +0100
            Re: CVE-2017-5754 - ETA? Vincent Lefevre <vincent@vinc17.net> - 2018-01-12 22:50 +0100
              Re: CVE-2017-5754 - XEN silent_disable? bw <bwtnguy@yahoo.com> - 2018-01-13 02:10 +0100
                Re: CVE-2017-5754 - XEN silent_disable? <tomas@tuxteam.de> - 2018-01-13 08:30 +0100
                Re: CVE-2017-5754 - XEN silent_disable? Vincent Lefevre <vincent@vinc17.net> - 2018-01-13 10:50 +0100
                Re: CVE-2017-5754 - XEN silent_disable? <tomas@tuxteam.de> - 2018-01-13 12:30 +0100
              Re: CVE-2017-5754 - ETA? Tixy <tixy@yxit.co.uk> - 2018-01-13 09:10 +0100
                Re: CVE-2017-5754 - ETA? Tixy <tixy@yxit.co.uk> - 2018-01-13 09:50 +0100

csiph-web