* Re: [PATCH] Watchdog: fix pretimeout noop governor logging and description
2026-06-16 17:19 [PATCH] Watchdog: fix pretimeout noop governor logging and description Lorenzo Egidio
@ 2026-06-16 17:20 ` sashiko-bot
2026-06-16 18:44 ` Guenter Roeck
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: sashiko-bot @ 2026-06-16 17:20 UTC (permalink / raw)
To: Lorenzo Egidio; +Cc: linux-watchdog
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch leaves the `%d` format specifier in the `pr_alert` string but removes the corresponding argument.
--
commit 0327e7d6697fa21e6b3ac5f9311da43e2ca86831
Author: Lorenzo Egidio <lorenzoegidioms@gmail.com>
Watchdog: fix pretimeout noop governor logging and description
This commit updates the watchdog pretimeout noop governor by removing
the usage of wdd->id to avoid potential compilation issues on different
kernel versions. It also corrects the module description to match the
governor's name.
> diff --git a/drivers/watchdog/pretimeout_noop.c b/drivers/watchdog/pretimeout_noop.c
> index 74ec02b9ffca4..ddb5192fb06bc 100644
> --- a/drivers/watchdog/pretimeout_noop.c
> +++ b/drivers/watchdog/pretimeout_noop.c
> @@ -17,7 +17,7 @@
> */
> static void pretimeout_noop(struct watchdog_device *wdd)
> {
> - pr_alert("watchdog%d: pretimeout event\n", wdd->id);
> + pr_alert("watchdog%d: pretimeout event\n");
[Severity: Medium]
Does this leave a format specifier without a corresponding argument?
The commit message suggested changing the string to
"watchdog: pretimeout event\n", but the %d is still present in the format
string. This will likely cause pr_alert() to read an uninitialized integer
from the stack or a register, resulting in garbage values being printed to
the kernel log.
> }
>
> static struct watchdog_governor watchdog_gov_noop = {
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260616171955.658-1-lorenzoegidioms@gmail.com?part=1
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] Watchdog: fix pretimeout noop governor logging and description
2026-06-16 17:19 [PATCH] Watchdog: fix pretimeout noop governor logging and description Lorenzo Egidio
2026-06-16 17:20 ` sashiko-bot
@ 2026-06-16 18:44 ` Guenter Roeck
2026-06-17 4:30 ` kernel test robot
2026-06-17 4:34 ` kernel test robot
3 siblings, 0 replies; 5+ messages in thread
From: Guenter Roeck @ 2026-06-16 18:44 UTC (permalink / raw)
To: Lorenzo Egidio, linux-watchdog, wim; +Cc: linux-kernel
On 6/16/26 10:19, Lorenzo Egidio wrote:
> Overview
> This review is dedicated to a pretimeout governor implementation of Linux kernel watchdog ("noop"). The overall module organization and the registration mechanism are done rightly and in accordance with the kernel standards. But, two points were noticed that could result in either compilation errors or difficulties in maintainability.
> 1. Potential problem: pr_alert usage with the wdd->id
> Within the callback function:
> static void pretimeout_noop(struct watchdog_device *wdd) { pr_alert("watchdog%d: pretimeout event\n", wdd->id); }
> Problem
> The id field of the struct watchdog_device is not ensured to be present in all Linux kernel versions. Actually, in many recent kernel versions, this field is either missing or not exposed in the public structure API.
> Consequence
> Compilation may fail with the following error at compile time:error: 'struct watchdog_device' has no member named 'id'
> Portability of the code to different kernel versions is lessened as it depends on the details of the internal structure.
>
Your AI doesn't know what it is talking about.
> Suggestions
> Do not directly access wdd->id. It is better to use a general message or a stable field which is safe across versions if available.
> An example of a safe alternative:
> pr_alert("watchdog: pretimeout event\n");
> 2. Mismatch in MODULE_DESCRIPTION
> The present module declares:
> MODULE_DESCRIPTION("Panic watchdog pretimeout governor");
> Problem
> There is a difference between the module description and the very name of the governor:
> .name = "noop"
> The code clearly states a "noop" governor, but the description talks about a "panic" governor, thereby causing misunderstanding.
> Result
> Developers and maintainers get confused
> The module metadata is not correctly described
> There is a decrease in clarity in logs and documentation
>
> Suggestion
> Correct the module description to be in line with the actual operation of the implementation.
> Example:
> MODULE_DESCRIPTION("Noop watchdog pretimeout governor");
> Conclusion
> The implementation is good structurally and it fits well with the Linux kernel watchdog governor framework. On the other hand, the usage of wdd->id could result in the incompatibility problem with the different kernel versions and the module metadata carries a description inconsistency that has to be fixed for the better clarity and maintainability.
>
> Signed-off-by: Lorenzo Egidio <lorenzoegidioms@gmail.com>
> ---
> drivers/watchdog/pretimeout_noop.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/watchdog/pretimeout_noop.c b/drivers/watchdog/pretimeout_noop.c
> index 74ec02b9f..ddb5192fb 100644
> --- a/drivers/watchdog/pretimeout_noop.c
> +++ b/drivers/watchdog/pretimeout_noop.c
> @@ -17,7 +17,7 @@
> */
> static void pretimeout_noop(struct watchdog_device *wdd)
> {
> - pr_alert("watchdog%d: pretimeout event\n", wdd->id);
> + pr_alert("watchdog%d: pretimeout event\n");
Seriously ? Your commit description is obviously AI generated,
and (hopefully) so is this code. And, even more obviously,
you did not even try to compile it, or you ignored the error/warning
produced by the compile attempt. And the reasoning is completely
wrong.
Please stop wasting my time.
Guenter
> }
>
> static struct watchdog_governor watchdog_gov_noop = {
> @@ -38,5 +38,5 @@ module_init(watchdog_gov_noop_register);
> module_exit(watchdog_gov_noop_unregister);
>
> MODULE_AUTHOR("Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>");
> -MODULE_DESCRIPTION("Panic watchdog pretimeout governor");
> +MODULE_DESCRIPTION("Noop watchdog pretimeout governor");
> MODULE_LICENSE("GPL");
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] Watchdog: fix pretimeout noop governor logging and description
2026-06-16 17:19 [PATCH] Watchdog: fix pretimeout noop governor logging and description Lorenzo Egidio
2026-06-16 17:20 ` sashiko-bot
2026-06-16 18:44 ` Guenter Roeck
@ 2026-06-17 4:30 ` kernel test robot
2026-06-17 4:34 ` kernel test robot
3 siblings, 0 replies; 5+ messages in thread
From: kernel test robot @ 2026-06-17 4:30 UTC (permalink / raw)
To: Lorenzo Egidio, linux-watchdog, linux, wim
Cc: oe-kbuild-all, linux-kernel, Lorenzo Egidio
Hi Lorenzo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon]
[also build test WARNING on groeck-staging/hwmon-next groeck-staging/watchdog groeck-staging/watchdog-next linus/master v7.1 next-20260616]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Egidio/Watchdog-fix-pretimeout-noop-governor-logging-and-description/20260617-032417
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon
patch link: https://lore.kernel.org/r/20260616171955.658-1-lorenzoegidioms%40gmail.com
patch subject: [PATCH] Watchdog: fix pretimeout noop governor logging and description
config: parisc-randconfig-001-20260617 (https://download.01.org/0day-ci/archive/20260617/202606171228.xMQDJyrF-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260617/202606171228.xMQDJyrF-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606171228.xMQDJyrF-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/asm-generic/bug.h:31,
from arch/parisc/include/asm/bug.h:97,
from include/linux/bug.h:5,
from include/linux/instrumented.h:10,
from include/linux/atomic/atomic-instrumented.h:17,
from include/linux/atomic.h:82,
from arch/parisc/include/asm/bitops.h:13,
from include/linux/bitops.h:67,
from include/linux/log2.h:12,
from include/asm-generic/div64.h:55,
from ./arch/parisc/include/generated/asm/div64.h:1,
from include/linux/math.h:6,
from include/linux/math64.h:6,
from include/linux/time.h:6,
from include/linux/stat.h:19,
from include/linux/module.h:13,
from drivers/watchdog/pretimeout_noop.c:6:
drivers/watchdog/pretimeout_noop.c: In function 'pretimeout_noop':
>> include/linux/kern_levels.h:5:25: warning: format '%d' expects a matching 'int' argument [-Wformat=]
5 | #define KERN_SOH "\001" /* ASCII Start Of Header */
| ^~~~~~
include/linux/printk.h:483:25: note: in definition of macro 'printk_index_wrap'
483 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~
include/linux/printk.h:534:9: note: in expansion of macro 'printk'
534 | printk(KERN_ALERT pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~
include/linux/kern_levels.h:9:25: note: in expansion of macro 'KERN_SOH'
9 | #define KERN_ALERT KERN_SOH "1" /* action must be taken immediately */
| ^~~~~~~~
include/linux/printk.h:534:16: note: in expansion of macro 'KERN_ALERT'
534 | printk(KERN_ALERT pr_fmt(fmt), ##__VA_ARGS__)
| ^~~~~~~~~~
drivers/watchdog/pretimeout_noop.c:20:9: note: in expansion of macro 'pr_alert'
20 | pr_alert("watchdog%d: pretimeout event\n");
| ^~~~~~~~
vim +5 include/linux/kern_levels.h
314ba3520e513a Joe Perches 2012-07-30 4
04d2c8c83d0e3a Joe Perches 2012-07-30 @5 #define KERN_SOH "\001" /* ASCII Start Of Header */
04d2c8c83d0e3a Joe Perches 2012-07-30 6 #define KERN_SOH_ASCII '\001'
04d2c8c83d0e3a Joe Perches 2012-07-30 7
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] Watchdog: fix pretimeout noop governor logging and description
2026-06-16 17:19 [PATCH] Watchdog: fix pretimeout noop governor logging and description Lorenzo Egidio
` (2 preceding siblings ...)
2026-06-17 4:30 ` kernel test robot
@ 2026-06-17 4:34 ` kernel test robot
3 siblings, 0 replies; 5+ messages in thread
From: kernel test robot @ 2026-06-17 4:34 UTC (permalink / raw)
To: Lorenzo Egidio, linux-watchdog, linux, wim
Cc: oe-kbuild-all, linux-kernel, Lorenzo Egidio
Hi Lorenzo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon]
[also build test WARNING on groeck-staging/hwmon-next groeck-staging/watchdog groeck-staging/watchdog-next linus/master v7.1 next-20260616]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Egidio/Watchdog-fix-pretimeout-noop-governor-logging-and-description/20260617-032417
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon
patch link: https://lore.kernel.org/r/20260616171955.658-1-lorenzoegidioms%40gmail.com
patch subject: [PATCH] Watchdog: fix pretimeout noop governor logging and description
config: i386-randconfig-141-20260617 (https://download.01.org/0day-ci/archive/20260617/202606171208.XDs3KbGh-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
smatch: v0.5.0-9185-gbcc58b9c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260617/202606171208.XDs3KbGh-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606171208.XDs3KbGh-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/watchdog/pretimeout_noop.c:20:21: warning: more '%' conversions than data arguments [-Wformat-insufficient-args]
20 | pr_alert("watchdog%d: pretimeout event\n");
| ~^
include/linux/printk.h:534:27: note: expanded from macro 'pr_alert'
534 | printk(KERN_ALERT pr_fmt(fmt), ##__VA_ARGS__)
| ^~~
include/linux/printk.h:401:21: note: expanded from macro 'pr_fmt'
401 | #define pr_fmt(fmt) fmt
| ^~~
include/linux/printk.h:511:53: note: expanded from macro 'printk'
511 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ^~~
include/linux/printk.h:483:11: note: expanded from macro 'printk_index_wrap'
483 | _p_func(_fmt, ##__VA_ARGS__); \
| ^~~~
1 warning generated.
vim +20 drivers/watchdog/pretimeout_noop.c
11
12 /**
13 * pretimeout_noop - No operation on watchdog pretimeout event
14 * @wdd: watchdog_device
15 *
16 * This function prints a message about pretimeout to kernel log.
17 */
18 static void pretimeout_noop(struct watchdog_device *wdd)
19 {
> 20 pr_alert("watchdog%d: pretimeout event\n");
21 }
22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] 5+ messages in thread