Project

General

Profile

Todo #9026

PTI checkbox wording can be confusing, should give a little more detail and show current PTI status

Added by Jim Pingle over 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Start date:
10/08/2018
Due date:
% Done:

100%

Estimated time:

Description

Now that there are Intel CPUs in the wild unaffected by Meltdown, PTI may default to disabled in cases where it is not clear to the user what is happening. The checkbox on system_advanced_misc.php implies that unchecked=on, checked=off, but in reality the option only forces it off, there is no way to force it on.

The wording of the message should also include that it requires a reboot to activate.

Associated revisions

Revision 2ba7026d (diff)
Added by Jim Pingle over 1 year ago

Wording changes for PTI disable option. Fixes #9026

Revision f4bc3bce (diff)
Added by Jim Pingle over 1 year ago

Wording changes for PTI disable option. Fixes #9026

(cherry picked from commit 2ba7026de2c08450fa40d5694f44cbe46a2262e2)

History

#1 Updated by Jim Pingle over 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by James Dekker over 1 year ago

Tested on 2.4.5.a.20181011.0014, text for Kernel PTI now reads:

Forcefully disable the kernel PTI Meltdown workaround. If disabled the kernel memory can be accessed by unprivileged users on affected CPUs. This option forces the workaround off, and requires a reboot to activate.

PTI is active by default only on affected CPUs, if PTI is disabled by default then this option will have no effect.
Current PTI status: Enabled

Before it was:

Disable the kernel PTI Meltdown workaround. If disabled the kernel memory can be accessed by unprivileged users on affected CPUs.

#3 Updated by Jim Pingle over 1 year ago

  • Status changed from Feedback to Resolved

#4 Updated by Corey Boyle about 1 year ago

Why even have the option to disable PTI?

#5 Updated by Jim Pingle about 1 year ago

Corey Boyle wrote:

Why even have the option to disable PTI?

The user may have a use case where the original problem is not relevant and they need the additional performance.

Also available in: Atom PDF