linux-kernel - Re: [RFC][PATCH] watchdog: rti-wdt: Provide set_timeout handler to make existing userspace happy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Mon, 22 Apr 2024 10:23:50 +0200
From: Francesco Dolcini <francesco@...cini.it>
To: Jan Kiszka <jan.kiszka@...mens.com>
CC: Wim Van Sebroeck <wim@...ux-watchdog.org>, Guenter Roeck <linux@...ck-us.net>,
 linux-watchdog@...r.kernel.org,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Tero Kristo <t-kristo@...com>,
 "Su, Bao Cheng (RC-CN DF FA R&D)" <baocheng.su@...mens.com>
Subject: Re: [RFC][PATCH] watchdog: rti-wdt: Provide set_timeout handler to make existing userspace happy



Il 22 aprile 2024 10:20:07 CEST, Francesco Dolcini <francesco@...cini.it> ha scritto:
>
>
>Il 22 aprile 2024 07:35:52 CEST, Jan Kiszka <jan.kiszka@...mens.com> ha scritto:
>>On 21.04.24 10:49, Francesco Dolcini wrote:
>>> On Mon, Sep 13, 2021 at 01:41:43PM +0200, Jan Kiszka wrote:
>>>> From: Jan Kiszka <jan.kiszka@...mens.com>
>>>>
>>>> Prominent userspace - systemd - cannot handle watchdogs without
>>>> WDIOF_SETTIMEOUT, even if it was configured to the same time as the
>>>> driver selected or was used by firmware to start the watchdog. To avoid
>>>> failing in this case, implement a handler that only fails if a deviating
>>>> set_timeout is requested.
>>>>
>>>> Signed-off-by: Jan Kiszka <jan.kiszka@...mens.com>
>>> 
>>> Are you aware of this patch https://lore.kernel.org/all/20240417205700.3947408-1-jm@ti.com/ ?
>>> 
>>
>>Thanks for the heads-up, we will surely try to test things on our setups
>>as well. But commenting on this dead and not directly related thread may
>>have caused some confusion...
>
>I was too terse.

And I did not realize your patch was from 2021. Sorry for the confusion.


Francesco