From: Kris Karas <linux-1993@moonlit-rail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: omar.kilani@gmail.com
Subject: Re: Weird issue with epoll and kernel >= 5.0
Date: Sat, 28 Mar 2020 15:18:12 -0400 [thread overview]
Message-ID: <72cde0de-6f4a-4928-d01b-1783ac3ee6e4@moonlit-rail.com> (raw)
In-Reply-To: <CA+8F9hhy=WPMJLQ3Ya_w4O6xyWk7KsXi=YJofmyC577_UJTutA@mail.gmail.com>
Hi Omar -
Omar Kilani wrote:
> I've observed an issue with epoll and kernels 5.0 and above when a
> system is generating a lot of epoll events.
It's tough getting an audience here on LK, unless you happen to
cross-post to one of the very specific mailing lists (or directly to
individuals) who maintain a particular subsystem. I just rejoined LK
after a 15 year hiatus; it's a rather different neighborhood. *cough*
But I digress.
My first question on your issue is, after booting, how long does it take
to show up? Can you reproduce it fairly easily? If the answer is
"Yes," and you seem to be able to afford the resources for a multi-CPU
VM, then making a bisecting run would likely narrow it down to something
you could then email directly to the relevant maintainer.
If you are not already familiar with bisecting, the git documentation on
bisecting is the definitive reference:
https://git-scm.com/docs/git-bisect
But it is quite long. You can usually find a more abbreviated version
by googling for "<yourdistroname> git bisect"; the ones for Arch and
Ubuntu are pretty decent.
Once you know which file is relevant, you can run:
$ ./scripts/get_maintainer.pl --file drivers/foo/bar.c
... or whatever "git bisect" says is the culprit file, and use the
script output as the To: for your email message.
Good luck!
Kris
next prev parent reply other threads:[~2020-03-28 19:18 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 [this message]
2020-03-28 19:21 ` Randy Dunlap
2020-03-29 12:09 ` David Laight
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=72cde0de-6f4a-4928-d01b-1783ac3ee6e4@moonlit-rail.com \
--to=linux-1993@moonlit-rail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.kilani@gmail.com \
/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®