From: "chaithco@redhat.com" <chaithco@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: wim@linux-watchdog.org, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Differentiate scenarios when watchdog is closed
Date: Mon, 31 Aug 2026 14:05:20 -0600 [thread overview]
Message-ID: <df49394b45f04e0de5ab0300a8d18f5ba6d38b01.camel@redhat.com> (raw)
In-Reply-To: <93d22742-bf3e-4e69-aed5-27137d8f49bf@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Thu, 2026-08-27 at 11:10 -0700, Guenter Roeck wrote:
> Problem is that we don't know if "something bad happened". The same
> message
> will be seen if the watchdog daemon was killed or crashed. We can not
> just
> assume that closing the watchdog device was intentional.
That's the same sticking point I've come across. Differentiating
between positive intentional closure versus malicious or buggy closure
would somehow need to be communicated to the kernel. It makes more
sense that users of the watchdog which intend to close the watchdog
while still running maybe denote such. I opened a PR with systemd at
https://github.com/systemd/systemd/pull/43552 to see if there was some
way this could be tackled from that perspective.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-31 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 20:50 Charles Haithcock
2026-08-27 16:01 ` Guenter Roeck
2026-08-27 17:09 ` chaithco
2026-08-27 18:10 ` Guenter Roeck
2026-08-31 20:05 ` chaithco [this message]
2026-09-01 16:06 ` Guenter Roeck
2026-09-01 21:44 ` chaithco
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=df49394b45f04e0de5ab0300a8d18f5ba6d38b01.camel@redhat.com \
--to=chaithco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
/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
all inboxes | Powered by JetHome®