Hardware watchdog resets system before completing a core dump

[lucasmr]

Describe the bug
When triggering a core dump with TASK_WDT_HW_FALLBACK, it's possible the hardware watchdog resets the system before the dump completes, especially on slow logging backends. The maximum TASK_WDT_HW_FALLBACK_DELAY of 1s is not enough in my case.

To Reproduce

1. Trigger a core dump with a lot of data over a slow logging backend.

Expected behavior
Core dump completes successfully.

Impact
To circumvent this, setting TASK_WDT_MIN_TIMEOUT to a big enough number works, however it's confusing to the user, especially because this should be used for the intended purpose of setting the minimum timeout of all tasks. Letting the user have a big enough TASK_WDT_HW_FALLBACK_DELAY would be cleaner.

[github-actions]

Hi @lucasmr! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.