improve handling of errors returned by kthread_park()
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | watchdog: fix error handling in proc_watchdog_thresh()kernel/ | +4 | 1 reply | |
| 2/5 | watchdog: move watchdog_disable_all_cpus() outside of ifdefkernel/ | +5 | 2 replies | |
| 3/5 | watchdog: implement error handling in update_watchdog_all_cpus() and callerskernel/ | +23 | 1 reply | |
| 4/5 | watchdog: implement error handling in lockup_detector_suspend()kernel/ | +5 | 1 reply | |
| 5/5 | watchdog: do not unpark threads in watchdog_park_threads() on errorkernel/ | +6 | 1 reply |
Reviews trailers per patch
All 5 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Aaron Tomlin | Don Zickus |
|---|---|---|
| Series | A-b | |
| 1/5 | R-b | |
| 2/5 | R-b | |
| 3/5 | R-b | |
| 4/5 | R-b | |
| 5/5 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] improve handling of errors returned by kthread_park()
The original watchdog_park_threads() function that was introduced by commit 81a4beef91ba4a9e8ad6054ca9933dff7e25ff28 takes a very simple approach to handle errors returned by kthread_park(): It attempts to roll back all watchdog threads to the unparked state. However, this may be undesired behaviour from the perspective of the caller which may want to handle errors as appropriate in its specific context. Currently, there are two possible call chains:
- watchdog suspend/resume interface
lockup_detector_suspend
watchdog_park_threads
- write to parameters in /proc/sys/kernel
proc_watchdog_update
watchdog_enable_all_cpus
update_watchdog_all_cpus
watchdog_park_threads
Instead of 'blindly' attempting to unpark the watchdog threads if a kthread_park() call fails, the new approach is to disable the lockup detectors in the above call chains. Failure becomes visible to the user as follows:
- error messages from lockup_detector_suspend()
or watchdog_enable_all_cpus()
- the state that can be read from /proc/sys/kernel/watchdog_enabled
- the 'write' system call in the latter call chain returns an error
Ulrich Obergfell (5):
watchdog: fix error handling in proc_watchdog_thresh()
watchdog: move watchdog_disable_all_cpus() outside of ifdef
watchdog: implement error handling in update_watchdog_all_cpus() and
callers
watchdog: implement error handling in lockup_detector_suspend()
watchdog: do not unpark threads in watchdog_park_threads() on error
kernel/watchdog.c | 60 +++++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 43 insertions(+), 17 deletions(-)
Signature · 1 line
1.7.11.7