Comment 5 for bug 765082

Is there any plan on backporting the fix for this issue, even if "cosmetic" ?

I would imagine it could be a problem in some cases where the load average or number of I/O wait processes is monitored.

Most monitoring scripts assume that a load average higher than the maximum number of possible threads should trigger a warning.
Quite a lot of scripts looking for I/O issues are also looking for processes in "D" state and so will wrongly flag ips-monitor as being the reason of slow disk access (or similar).