Allow individual features to be locked down
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 18 repliesIn review
- v12 patches 10 repliesSuperseded
Changes in v2 from the cover letter
* Added Patch 3 to incoroporate Serge's hardening suggestion
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | lockdown: Switch implementation to using bitmapsecurity/ | +12 | 3 replies | |
| 2/3 | lockdown/kunit: Introduce kunit testssecurity/ security/ security/ +1 more | +64 | 3 replies | |
| 3/3 | lockdown: Use snprintf in lockdown_readsecurity/ | +10 | 3 replies |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Serge Hallyn |
|---|---|
| 1/3 | R-b |
| 2/3 | R-b |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/3] Allow individual features to be locked down
This simple change allows usecases where someone might want to lock only specific feature at a finer granularity than integrity/confidentiality levels allows. The first likely user of this is the CoCo subsystem where certain features will be disabled.
Changes since v1:
* Added Patch 3 to incoroporate Serge's hardening suggestion
Nikolay Borisov (3):
lockdown: Switch implementation to using bitmap
lockdown/kunit: Introduce kunit tests
lockdown: Use snprintf in lockdown_read
security/lockdown/Kconfig | 5 +++ security/lockdown/Makefile | 1 + security/lockdown/lockdown.c | 36 +++++++++++++++------ security/lockdown/lockdown_test.c | 54 +++++++++++++++++++++++++++++++ 4 files changed, 86 insertions(+), 10 deletions(-) create mode 100644 security/lockdown/lockdown_test.c
--
2.34.1