From: Eric Wong <e@80x24.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>,
Arnd Bergmann <arnd@arndb.de>, Al Viro <viro@zeniv.linux.org.uk>,
Jason Baron <jbaron@akamai.com>,
linux-kernel@vger.kernel.org, Omar Kilani <omar.kilani@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Strange issues with epoll since 5.0
Date: Mon, 29 Apr 2019 21:04:27 +0000 [thread overview]
Message-ID: <20190429210427.dmfemfft2t2gdwko@dcvr> (raw)
In-Reply-To: <20190429204754.hkz7z736tdk4ucum@linux-r8p5>
Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Sun, 28 Apr 2019, Eric Wong wrote:
>
> > Just running one test won't trigger since it needs a busy
> > machine; but:
> >
> > make test/mgmt_auto_adjust.log
> > (and "rm make test/mgmt_auto_adjust.log" if you want to rerun)
>
> fyi no luck reproducing on both either a large (280) or small (4 cpu)
> machine, I'm running it along with a kernel build overcommiting cpus x2.
Thanks for taking a look.
> Is there any workload in particular you are using to stress the box?
Just the "make -j$N check" I mentioned up-thread which spawns a
lot of tests in parallel. For the small 4 CPU machine,
-j32 or -j16 ought to be reproducing the problem.
I'll try to set aside some time this week to get familiar with
kernel internals w.r.t. signal handling.
next prev parent reply other threads:[~2019-04-29 21:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+8F9hicnF=kvjXPZFQy=Pa2HJUS3JS+G9VswFHNQQynPMHGVQ@mail.gmail.com>
[not found] ` <20190424193903.swlfmfuo6cqnpkwa@dcvr>
2019-04-27 9:33 ` Strange issues with epoll since 5.0 Eric Wong
2019-04-27 23:31 ` Deepa Dinamani
2019-04-28 0:48 ` Eric Wong
2019-04-29 20:47 ` Davidlohr Bueso
2019-04-29 21:04 ` Eric Wong [this message]
2019-04-30 21:07 ` Deepa Dinamani
2019-05-01 2:14 ` Eric Wong
2019-05-01 2:26 ` Eric Wong
2019-05-01 7:39 ` Eric Wong
2019-05-01 18:37 ` Deepa Dinamani
2019-05-01 20:48 ` Eric Wong
2019-05-01 20:53 ` Deepa Dinamani
2019-05-03 0:01 ` Deepa Dinamani
2019-05-03 2:34 ` Eric Wong
2019-05-03 3:34 ` Davidlohr Bueso
2019-05-03 3:42 ` [PATCH] signal: Adjust error codes according to restore_user_sigmask() Deepa Dinamani
2019-05-03 6:34 ` Eric Wong
2019-05-03 18:21 ` Deepa Dinamani
2019-05-03 19:51 ` Davidlohr Bueso
2019-05-03 22:53 ` Deepa Dinamani
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=20190429210427.dmfemfft2t2gdwko@dcvr \
--to=e@80x24.org \
--cc=arnd@arndb.de \
--cc=dave@stgolabs.net \
--cc=deepa.kernel@gmail.com \
--cc=jbaron@akamai.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.kilani@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).