linux-kernel - RE: [PATCH v4 1/3] watchdog: aspeed: Update bootstatus handling

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]

Message-ID:
 <TYZPR06MB52039AB24714A400FF266024B2042@TYZPR06MB5203.apcprd06.prod.outlook.com>
Date: Tue, 17 Dec 2024 02:15:18 +0000
From: Chin-Ting Kuo <chin-ting_kuo@...eedtech.com>
To: Andrew Jeffery <andrew@...econstruct.com.au>, Guenter Roeck
	<linux@...ck-us.net>, Patrick Williams <patrick@...cx.xyz>,
	"wim@...ux-watchdog.org" <wim@...ux-watchdog.org>
CC: "joel@....id.au" <joel@....id.au>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-aspeed@...ts.ozlabs.org"
	<linux-aspeed@...ts.ozlabs.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "linux-watchdog@...r.kernel.org"
	<linux-watchdog@...r.kernel.org>, "Peter.Yin@...ntatw.com"
	<Peter.Yin@...ntatw.com>, "Patrick_NC_Lin@...ynn.com"
	<Patrick_NC_Lin@...ynn.com>, "Bonnie_Lo@...ynn.com" <Bonnie_Lo@...ynn.com>,
	"DELPHINE_CHIU@...ynn.com" <DELPHINE_CHIU@...ynn.com>, BMC-SW
	<BMC-SW@...eedtech.com>, "chnguyen@...erecomputing.com"
	<chnguyen@...erecomputing.com>
Subject: RE: [PATCH v4 1/3] watchdog: aspeed: Update bootstatus handling

Hi Andrew,

> -----Original Message-----
> From: Andrew Jeffery <andrew@...econstruct.com.au>
> Sent: Wednesday, November 20, 2024 12:54 PM
> Subject: Re: [PATCH v4 1/3] watchdog: aspeed: Update bootstatus handling
> 
> On Mon, 2024-11-18 at 17:27 -0800, Guenter Roeck wrote:
> > So, again, what exactly would userspace do with the information that
> > this was a watchdog triggered warm reboot ? Why would it need that
> > information ?
> 
> I'll defer to the others on To/Cc to answer that.
> 
> My only position is I don't think changing behaviour of existing drivers to
> exploit WDIOF_EXTERN1 as a graceful-reboot indicator is a good idea either.
> Obviously I don't have much skin in the game with watchdog maintenance, so
> my thoughts shouldn't have much influence beyond the Aspeed-specifics, but I
> just didn't want to see some fun new confusion or incompatibility arise as a
> result.
> 
Agree to your misgiving, in the next patches, only two categories, "Power on reset"
and "WDT reset" (Card reset), will be taken into consideration. The graceful-reboot
scenario will be postponed to the patches in the future.


Thanks,
Chin-Ting