pti should default to on
Bug #1887008 reported by
Andrea Ieri
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-sysconfig |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
The sysconfig charm allows users to choose between pti=on and pti=off, but defaults to off.
I think the charm should do the opposite. This is for two reasons:
1. the Ubuntu kernel defaults to pti=on
2. pti is used as a meltdown mitigation strategy and as such it should not be disabled without the explicit consent of the operator. Having a default of pti=off will make several operators disable it inadvertently just by installing the charm
Related branches
~dparv/charm-sysconfig:bug_1887008
- 🤖 prod-jenkaas-bootstack: Approve (continuous-integration)
- James Troup (community): Needs Fixing
- BootStack Reviewers: Pending requested
-
Diff: 326 lines (+62/-34)11 files modifiedMakefile (+4/-0)
src/README.md (+4/-2)
src/actions.yaml (+3/-0)
src/actions/update-grub (+8/-0)
src/config.yaml (+5/-3)
src/lib/lib_sysconfig.py (+8/-2)
src/reactive/sysconfig.py (+1/-1)
src/templates/grub.j2 (+2/-2)
src/tests/functional/test_deploy.py (+15/-19)
src/tests/unit/test_lib.py (+6/-5)
src/tox.ini (+6/-0)
| description: | updated |
| Changed in charm-sysconfig: | |
| importance: | Undecided → Medium |
| Changed in charm-sysconfig: | |
| status: | New → Triaged |
| Changed in charm-sysconfig: | |
| status: | Triaged → Fix Committed |
| Changed in charm-sysconfig: | |
| status: | Fix Committed → Fix Released |
| milestone: | none → 22.01 |
| tags: | added: bseng-63 |
To post a comment you must log in.
