How was "120" chosen for CONFIG_DEFAULT_HUNG_TASK_TIMEOUT?

From: Mailing Lists
Date: Fri May 27 2016 - 07:26:53 EST


I'm trying to understand how this value has been chosen.
Was it arbitrary, or did it come up after some rationale?

If alter it to a lower value like 30 (or 60), and a piece of third
party code hung in D state triggers the kernel hung task complain
message, can I still report this as an issue to that code's issue
tracker even if the message is not shown at default value of 120?


Please cc me for replies, as I'm not subscribed.