Skip to content

Explain panic() calls for keyring initialization

Mickaël Salaün keyrings linux-crypto lkml 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest1 patch 3 repliesIn review
  2. v11 patch 6 repliesSuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/1certs: Explain the rationale to call panic()certs/blacklist.c+9 -03 replies

Reviews trailers per patch

The patch has a Reviewed-by or Acked-by.

PatchJarkko SakkinenPaul MooreTyler Hicks
1/1Requested-by R-b R-b R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.

Read the v2 thread

Cover letter [PATCH v2 0/1] Explain panic() calls for keyring initialization

As suggested by Jarkko and explained by Paul, let's document the panic() calls from the blacklist keyring initialization. This series applies on top of commit 50c486fe3108 ("certs: Allow root user to append signed hashes to the blacklist keyring"). This can smoothly be rebased on top of Jarkko's next branch.

This second version fixes some minor spelling issues.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?id=50c486fe310890c134b5cb36cf9a4135475a6074

Previous version:
https://lore.kernel.org/r/[email protected]

Regards,

Mickaël Salaün (1):
certs: Explain the rationale to call panic()

 certs/blacklist.c | 9 +++++++++
 1 file changed, 9 insertions(+)

base-commit: 50c486fe310890c134b5cb36cf9a4135475a6074

Signature · 1 line
2.35.1