Red Hat Bugzilla – Bug 994168
Reading /proc/timer_list with small buffers never finishes
Last modified: 2013-09-20 09:11:49 EDT
Description of problem:
Reading /proc/timer_list with small buffers never returns; e.g.
dd if=/proc/timer_list bs=10
This causes regression in a program (dropbearkey) which reads /proc/timer_list to fill its entropy pool. This worked with previous kernels (last tested with 3.4).
Version-Release number of selected component (if applicable):
this is fixed via:
Author: Nathan Zimmer <email@example.com>
Date: Wed Aug 28 16:35:14 2013 -0700
timer_list: correct the iterator for timer_list
Correct an issue with /proc/timer_list reported by Holger.
When reading from the proc file with a sufficiently small buffer, 2k so
not really that small, there was one could get hung trying to read the
file a chunk at a time.
The timer_list_start function failed to account for the possibility that
the offset was adjusted outside the timer_list_next.
Signed-off-by: Nathan Zimmer <firstname.lastname@example.org>
Reported-by: Holger Hans Peter Freyther <email@example.com>
Cc: John Stultz <firstname.lastname@example.org>
Cc: Thomas Gleixner <email@example.com>
Cc: Berke Durak <firstname.lastname@example.org>
Cc: Jeff Layton <email@example.com>
Tested-by: Al Viro <firstname.lastname@example.org>
Cc: <email@example.com> # 3.10.x
Signed-off-by: Andrew Morton <firstname.lastname@example.org>
Signed-off-by: Linus Torvalds <email@example.com>
From a quick look it hasn't hit 3.10.10 yet but I assume it will end in the next one.
It is in 3.10.11:
* b3772c8 - (2013-09-07 22:09:58 -0700) timer_list: correct the iterator for timer_list <Nathan Zimmer>
$ git tag --contains b3772c8
So this can be closed with the next update
*********** MASS BUG UPDATE **************
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.
Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.
If you experience different issues, please open a new bug report for those.
Josh, this one can be closed.
Yep, thank you.