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


Groups > linux.debian.kernel > #59932 > unrolled thread

Bug#886822: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo

Started byApollon Oikonomopoulos <apoikos@debian.org>
First post2018-01-10 11:20 +0100
Last post2018-01-10 19:20 +0100
Articles 4 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#886822: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo Apollon Oikonomopoulos <apoikos@debian.org> - 2018-01-10 11:20 +0100
    Processed: linux: KPTI backport lacks pti-related flags in  /proc/cpuinfo "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-01-10 11:20 +0100
    Bug#886822: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo Apollon Oikonomopoulos <apoikos@debian.org> - 2018-01-10 13:40 +0100
    Bug#886822: marked as done (linux: KPTI backport lacks  pti-related flags in /proc/cpuinfo) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-01-10 19:20 +0100

#59932 — Bug#886822: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo

FromApollon Oikonomopoulos <apoikos@debian.org>
Date2018-01-10 11:20 +0100
SubjectBug#886822: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo
Message-ID<v6lEd-gR-1@gated-at.bofh.it>
Source: linux
Version: 4.9.65-3+deb9u2
Severity: wishlist
Control: found -1 3.16.51-3+deb8u1

Dear Maintainer,

The backport of KPTI/KAISER to 4.9 and 3.16 lacks the pti CPU flag and 
the cpu_insecure bug found in /proc/cpuinfo in 4.14. While this does not 
affect core KPTI functionality, it makes it harder to determine whether 
a system is running with pti enabled without examining kernel logs.

Please consider backporting the relevant changes.

Regards,
Apollon

[toc] | [next] | [standalone]


#59933 — Processed: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2018-01-10 11:20 +0100
SubjectProcessed: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo
Message-ID<v6lEd-gR-5@gated-at.bofh.it>
In reply to#59932
Processing control commands:

> found -1 3.16.51-3+deb8u1
Bug #886822 [src:linux] linux: KPTI backport lacks pti-related flags in /proc/cpuinfo
Marked as found in versions linux/3.16.51-3+deb8u1.

-- 
886822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886822
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#59936

FromApollon Oikonomopoulos <apoikos@debian.org>
Date2018-01-10 13:40 +0100
Message-ID<v6nPH-1V9-9@gated-at.bofh.it>
In reply to#59932
On 12:06 Wed 10 Jan     , Apollon Oikonomopoulos wrote:
> The backport of KPTI/KAISER to 4.9 and 3.16 lacks the pti CPU flag and 
> the cpu_insecure bug found in /proc/cpuinfo in 4.14. While this does 
> not affect core KPTI functionality, it makes it harder to determine 
> whether a system is running with pti enabled without examining kernel 
> logs.

Correcting myself:

The flag is there, but it's called "kaiser" and not "pti". This seems to 
be the same throughout upstream backports of the patchset.

Feel free to close this bug report if you wish!

Regards,
Apollon

[toc] | [prev] | [next] | [standalone]


#59942 — Bug#886822: marked as done (linux: KPTI backport lacks pti-related flags in /proc/cpuinfo)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2018-01-10 19:20 +0100
SubjectBug#886822: marked as done (linux: KPTI backport lacks pti-related flags in /proc/cpuinfo)
Message-ID<v6t8K-5E9-17@gated-at.bofh.it>
In reply to#59932

[Multipart message — attachments visible in raw view] — view raw

Your message dated Wed, 10 Jan 2018 18:13:56 +0000
with message-id <1515608036.13978.77.camel@decadent.org.uk>
and subject line Re: Bug#886822: linux: KPTI backport lacks pti-related flags in /proc/cpuinfo
has caused the Debian Bug report #886822,
regarding linux: KPTI backport lacks pti-related flags in /proc/cpuinfo
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
886822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886822
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web