linux-kernel - RE: [PATCH v6 2/5] watchdog: s3c2410_wdt: Fix max

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <06c401dc284e$2bec2a50$83c47ef0$@samsung.com>
Date: Thu, 18 Sep 2025 09:11:47 +0530
From: "Alim Akhtar" <alim.akhtar@...sung.com>
To: "'Sangwook Shin'" <sw617.shin@...sung.com>, <krzk@...nel.org>,
	<wim@...ux-watchdog.org>, <linux@...ck-us.net>,
	<semen.protsenko@...aro.org>, <dongil01.park@...sung.com>,
	<khwan.seo@...sung.com>
Cc: <linux-arm-kernel@...ts.infradead.org>,
	<linux-samsung-soc@...r.kernel.org>, <linux-watchdog@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v6 2/5] watchdog: s3c2410_wdt: Fix max_timeout being
 calculated larger

Hi Sangwook

> -----Original Message-----
> From: Sangwook Shin <sw617.shin@...sung.com>
> Sent: Monday, August 18, 2025 7:48 AM
> To: krzk@...nel.org; alim.akhtar@...sung.com; wim@...ux-watchdog.org;
> linux@...ck-us.net; semen.protsenko@...aro.org;
> dongil01.park@...sung.com; khwan.seo@...sung.com
> Cc: linux-arm-kernel@...ts.infradead.org; linux-samsung-soc@...r.kernel.org;
> linux-watchdog@...r.kernel.org; linux-kernel@...r.kernel.org; Sangwook Shin
> <sw617.shin@...sung.com>
> Subject: [PATCH v6 2/5] watchdog: s3c2410_wdt: Fix max_timeout being
> calculated larger
> 
> Fix the issue of max_timeout being calculated larger than actual value.
> The calculation result of freq / (S3C2410_WTCON_PRESCALE_MAX + 1) /
> S3C2410_WTCON_MAXDIV is smaller than the actual value because the
> remainder is discarded during the calculation process. This leads to a larger
> calculated value for max_timeout compared to the actual settable value.
> To resolve this issue, the order of calculations in the computation process has
> been adjusted.
> 
> Reviewed-by: Sam Protsenko <semen.protsenko@...aro.org>
> Signed-off-by: Sangwook Shin <sw617.shin@...sung.com>
> ---
Reviewed-by: Alim Akhtar <alim.akhtar@...sung.com>