[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

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
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
On Wed, 2018-01-10 at 12:06 +0200, Apollon Oikonomopoulos wrote:
> 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.

Sorry, no, there is no infrastructure for this in older versions.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: