On 2018-12-12 03:03, Roman Penyaev wrote:
All coming events are stored in FIFO order and this is also should be
applicable to ->ovflist, which originally is stack, i.e. LIFO.
Thus to keep correct FIFO order ->ovflist should reversed by adding
elements to the head of the read list but not to the tail.
So the window for which the ovflist is used can be actually non-trivial
(ie lots of copy_to_user) and I just hope nobody out there is relying on
particular wakeup order. otoh nobody has every complained about this
"reverse" order and not having the perfect queue. And hopefully the same
will be for this case.
With that:
Reviewed-by: Davidlohr Bueso <dbu...@suse.de>
Signed-off-by: Roman Penyaev <rpeny...@suse.de>
Cc: Davidlohr Bueso <dbu...@suse.de>
Cc: Jason Baron <jba...@akamai.com>
Cc: Al Viro <v...@zeniv.linux.org.uk>
Cc: Andrew Morton <a...@linux-foundation.org>
Cc: Linus Torvalds <torva...@linux-foundation.org>
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
fs/eventpoll.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/eventpoll.c b/fs/eventpoll.c
index 2329f96469e2..3627c2e07149 100644
--- a/fs/eventpoll.c
+++ b/fs/eventpoll.c
@@ -722,7 +722,11 @@ static __poll_t ep_scan_ready_list(struct
eventpoll *ep,
* contain them, and the list_splice() below takes care of them.
*/
if (!ep_is_linked(epi)) {
- list_add_tail(&epi->rdllink, &ep->rdllist);
+ /*
+ * ->ovflist is LIFO, so we have to reverse it in order
+ * to keep in FIFO.
+ */
+ list_add(&epi->rdllink, &ep->rdllist);
ep_pm_stay_awake(epi);
}
}
