From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Ivan Mikhaylov <i.mikhaylov@yadro.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: watchdog start on restart
Date: Wed, 2 Sep 2020 15:19:56 +0200 [thread overview]
Message-ID: <e04bc12d-4520-89db-699c-ad89fcdbf76e@csgroup.eu> (raw)
In-Reply-To: <d2343032814705f33cd81f18f45630bf327c0ff8.camel@yadro.com>
Le 02/09/2020 à 15:02, Ivan Mikhaylov a écrit :
> Hello everyone. Currently, the watchdog interface only has "stop watchdog on
> restart" but lacks a "start watchdog on restart" one. Is there a way to achieve
> such functionality?
>
> I'd like to know why "stop watchdog on restart" wasn't implemented via ioctl
> interface? It would be more convenient from user perspective and you can
> control that behavior whenever you want from application layer.
>
> I have some thoughts on this problem that solve the aforementioned
> issue with "start watchdog on restart" but I don't think that my solution is
> correct.
>
I don't understand why a "start watchdog on restart" would be needed.
Isn't it the default expected behaviour for a watchdog ?
"stop watchdog on restart" is there to keep things under control during
a wanted machine reboot/restart, while still having the watchdog do its
job on an unexpected restart.
What would be the advantage of an ioctl() compared to the existing way ?
Christophe
next prev parent reply other threads:[~2020-09-02 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 13:02 Ivan Mikhaylov
2020-09-02 13:19 ` Christophe Leroy [this message]
2020-09-03 10:19 ` Ivan Mikhaylov
2020-09-02 13:36 ` Guenter Roeck
2020-09-03 10:23 ` Ivan Mikhaylov
2020-09-03 11:13 ` Christophe Leroy
2020-09-03 13:26 ` Ivan Mikhaylov
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=e04bc12d-4520-89db-699c-ad89fcdbf76e@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=i.mikhaylov@yadro.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®