Re: [PATCH] watchdog/hardlockup: reassign last_timestamp when enable nmi event

2019-10-13 Thread kbuild test robot
Hi Li, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [cannot apply to v5.4-rc2 next-20191010] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specif

Re: [PATCH] watchdog/hardlockup: reassign last_timestamp when enable nmi event

2019-10-13 Thread kbuild test robot
Hi Li, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [cannot apply to v5.4-rc2 next-20191011] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the

[PATCH] watchdog/hardlockup: reassign last_timestamp when enable nmi event

2019-10-12 Thread Li RongQing
last_timestamp is not initialized and is zero after boot, or stop to forward when nmi watchdog is disabled; and false positives still is possible when restart NMI timer after stopping 120 seconds so reassign last_timestamp always when enable nmi event Fixes: 7edaeb6841df ("kernel/watchdog: Preven