From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org,
Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>,
Pavel Machek <pavel@denx.de>
Subject: [PATCH 5.10.y-cip 0/2] watchdog: iTCO_wdt: Backport patches to enable handle_boot_enabled=0
Date: Tue, 18 Jul 2023 19:00:30 +0200 [thread overview]
Message-ID: <cover.1689699632.git.jan.kiszka@siemens.com> (raw)
These patches are needed in order to make iTCO_wdt respect
handle_boot_enabled=0, i.e. to step back from a running watchdog until
userspace picks it up. Up to 5.16, the driver simply stopped the
watchdog which could have created a non-monitored window during boot-up
in the handover from the firmware starting it to userspace (typically
sytemd) safely driving. E.g., any infinite loops in the initramfs would
could have created a locked-up system.
These patches were proposed to the watchdog maintainers for official
stable integration [1] but received no reaction so far. As the issue is critical for
CIP's OTA software update integration, let's use the CIP path instead.
I don't have any test setup for 4.19, so I'm only proposing this for
5.10 here.
Jan
[1] https://lore.kernel.org/linux-watchdog/e9c2d0a5-9618-b616-3be3-826cc0665388@siemens.com/T/#t
Mika Westerberg (2):
watchdog: iTCO_wdt: No need to stop the timer in probe
watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already
running
drivers/watchdog/iTCO_wdt.c | 26 +++++++++++++++++++++-----
1 file changed, 21 insertions(+), 5 deletions(-)
--
2.35.3
next reply other threads:[~2023-07-18 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 17:00 Jan Kiszka [this message]
2023-07-18 17:00 ` [PATCH 5.10.y-cip 1/2] watchdog: iTCO_wdt: No need to stop the timer in probe Jan Kiszka
2023-07-18 17:00 ` [PATCH 5.10.y-cip 2/2] watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running Jan Kiszka
2023-07-18 23:57 ` [PATCH 5.10.y-cip 0/2] watchdog: iTCO_wdt: Backport patches to enable handle_boot_enabled=0 nobuhiro1.iwamatsu
2023-07-19 11:23 ` Pavel Machek
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.1689699632.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
/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