Comment 4 for bug 1685512
Revision history for this message
| Paul Wise (Debian) (pabs) wrote Re: Fwd: iotop: upstream bug report | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Thu, 2017-05-04 at 11:17 +0300, Andrei C wrote:
> ChristianEhrhardt <email address hidden>
FYI, as you can see here this address only mails the bug report:
https:/
> Hope this helps to notify whoever is necessary.
Thanks for the ping, I usually look at Ubuntu iotop bugs only when I'm
about to make an upload to Debian, which hasn't happened for a while
because Guillaume Chazarain hasn't made a release recently.
> https:/
I think the issue is that iotop uses the current time to calculate
duration instead of using monotonically increasing time, which means
that when you change the time backwards, it gets a negative duration
and that causes some calculations to be incorrect.
Please test the attached patch and if it is correct I will include it
upstream and make an upload to Debian once stretch is released. The
patch can then be synced to Ubuntu. Please note that the patch relies
on Python 3.3 or later, so it won't work on anything older than trusty.
If it works then I'll try to make it work on more Python versions too.
tag patch
--
bye,
pabs
https:/