Skip to content

Allow individual features to be locked down

Nikolay Borisov linux-security-module lkml llvm oe-kbuild-all 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest3 patches 18 repliesIn review
  2. 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 filesSizeRepliesApplied
1/3lockdown: Switch implementation to using bitmapsecurity/lockdown/lockdown.c+12 -73 replies
2/3lockdown/kunit: Introduce kunit testssecurity/lockdown/Kconfig security/lockdown/Makefile security/lockdown/lockdown.c +1 more+64 -13 replies
3/3lockdown: Use snprintf in lockdown_readsecurity/lockdown/lockdown.c+10 -23 replies

Reviews trailers per patch

2 of 3 patches have a Reviewed-by or Acked-by.

PatchSerge Hallyn
1/3R-b
2/3R-b
3/3

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

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