From: Jens Axboe <[email protected]>
To: Andres Freund <[email protected]>,
[email protected], [email protected]
Subject: Re: liburing's eventfd test reliably oopses on 5.6-94f2630b1897
Date: Sun, 2 Feb 2020 12:07:51 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/2/20 9:56 AM, Andres Freund wrote:
> Hi,
>
> Updated to linus' current master (with just one perf build fix applied
> on top) for reasons unrelated to uring, got the oops below when running
> the uring tests. It's sufficient to just run the eventfd test.
This is known, I have a pending fix. I did gate the test on 5.6-rc, but
that'll only truly work once I ship those fixes out this week.
--
Jens Axboe
prev parent reply other threads:[~2020-02-02 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 16:56 liburing's eventfd test reliably oopses on 5.6-94f2630b1897 Andres Freund
2020-02-02 19:07 ` Jens Axboe [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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