From: David Laight <David.Laight@ACULAB.COM>
To: 'Randy Dunlap' <rdunlap@infradead.org>,
Omar Kilani <omar.kilani@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>
Subject: RE: Weird issue with epoll and kernel >= 5.0
Date: Sun, 29 Mar 2020 12:09:16 +0000 [thread overview]
Message-ID: <e31f945d6d854398b4236872d1636c41@AcuMS.aculab.com> (raw)
In-Reply-To: <34206eb5-1280-4aac-9a50-76f967646ca1@infradead.org>
From: Randy Dunlap
> Sent: 28 March 2020 19:22
...
> There have been around 10 changes in fs/eventpoll.c since v5.0 was
> released in March, 2019, so it would be helpful if you could test
> the latest mainline kernel to see if the problem is still present.
Is there any info about the scenarios that the fixes affect?
We've an application that can use epoll() or poll() and I wonder
if I should not default to epoll() on 5.0+ kernels that might be dodgy.
It rather depends whether wakeups just get lost - but the next
rx data will wake things up, or whether the linked lists get
completely hosed and 'all hell' breaks out (or doesn't).
In our case there is only one reader and the fd are all
UDP sockets (added and removed when the socket is created/closed).
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-03-29 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 18:10 Omar Kilani
2020-03-28 19:18 ` Kris Karas
2020-03-28 19:21 ` Randy Dunlap
2020-03-29 12:09 ` David Laight [this message]
2020-03-29 15:55 ` Randy Dunlap
2020-03-31 18:10 ` Davidlohr Bueso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e31f945d6d854398b4236872d1636c41@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.kilani@gmail.com \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®