From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: [isar-cip-core][PATCH 0/3] Service watchdog in initramfs-crypto-hook, harden watchdog settings
Date: Thu, 6 Jul 2023 10:04:25 +0200 [thread overview]
Message-ID: <cover.1688630668.git.jan.kiszka@siemens.com> (raw)
See patches for details.
Aside that, we still have an issue with the iTCO in 5.10 and older due
to a missing commit, see [1]. If upstream rejects stable as target, I
will propose the patches for -cip.
Jan
[1] https://lore.kernel.org/linux-watchdog/251a6e29-4ba1-73ed-d714-f35a2d3ee4b3@siemens.com/T/#t
Jan Kiszka (3):
initramfs-crypt-hook: Remove needless differences between clevis and
systemd scripts
initramfs-crypt-hook: Service watchdog while setting up the crypto
partitions
x86: Harden watchdog settings
.../files/encrypt_partition.clevis.script | 22 +++++++++--
.../files/encrypt_partition.env.tmpl | 2 +
.../files/encrypt_partition.systemd.hook | 2 +
.../files/encrypt_partition.systemd.script | 39 +++++++++++++------
.../initramfs-crypt-hook_0.1.bb | 7 +++-
wic/qemu-amd64-efibootguard-secureboot.wks.in | 2 +-
wic/x86-efibootguard.wks.in | 2 +-
7 files changed, 59 insertions(+), 17 deletions(-)
--
2.35.3
next reply other threads:[~2023-07-06 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 8:04 Jan Kiszka [this message]
2023-07-06 8:04 ` [isar-cip-core][PATCH 1/3] initramfs-crypt-hook: Remove needless differences between clevis and systemd scripts Jan Kiszka
2023-07-06 8:04 ` [isar-cip-core][PATCH 2/3] initramfs-crypt-hook: Service watchdog while setting up the crypto partitions Jan Kiszka
2023-07-10 9:11 ` Gylstorff Quirin
2023-07-10 10:14 ` Jan Kiszka
2023-07-10 10:44 ` Gylstorff Quirin
2023-07-10 11:23 ` [isar-cip-core][PATCH v2 " Jan Kiszka
2023-07-06 8:04 ` [isar-cip-core][PATCH 3/3] x86: Harden watchdog settings Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1688630668.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=quirin.gylstorff@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox