From: Jens Axboe <axboe@kernel.dk>
To: Glauber Costa <glauber@scylladb.com>,
io-uring@vger.kernel.org, Avi Kivity <avi@scylladb.com>
Subject: Re: crash on connect
Date: Thu, 20 Feb 2020 08:17:20 -0800 [thread overview]
Message-ID: <5e4904d5-e7fc-c079-e112-5b978c8fa129@kernel.dk> (raw)
In-Reply-To: <CAD-J=zbBU2j=a0t2zD7k_aGqguwwkzLpPnnrOUAm2DJ3ZUJFvg@mail.gmail.com>
On 2/20/20 7:19 AM, Glauber Costa wrote:
> Hi there, me again
>
> Kernel is at 043f0b67f2ab8d1af418056bc0cc6f0623d31347
>
> This test is easier to explain: it essentially issues a connect and a
> shutdown right away.
>
> It currently fails due to no fault of io_uring. But every now and then
> it crashes (you may have to run more than once to get it to crash)
>
> Instructions are similar to my last test.
> Except the test to build is now "tests/unit/connect_test"
> Code is at git@github.com:glommer/seastar.git branch io-uring-connect-crash
>
> Run it with ./build/release/tests/unit/connect_test -- -c1
> --reactor-backend=uring
>
> Backtrace attached
Perfect thanks, I'll take a look!
--
Jens Axboe
next prev parent reply other threads:[~2020-02-20 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 14:19 crash on connect Glauber Costa
2020-02-20 16:17 ` Jens Axboe [this message]
2020-02-20 16:29 ` Jens Axboe
2020-02-20 16:34 ` Glauber Costa
2020-02-20 16:38 ` Jens Axboe
2020-02-20 16:52 ` Glauber Costa
2020-02-20 17:28 ` Jens Axboe
2020-02-20 17:33 ` Glauber Costa
[not found] ` <CAD-J=zbdrZJ2nKgH3Ob=QAAM9Ci439T9DduNxvetK9B_52LDOQ@mail.gmail.com>
2020-02-20 19:12 ` Jens Axboe
2020-02-20 19:19 ` Glauber Costa
2020-02-20 19:36 ` Glauber Costa
2020-02-20 20:08 ` Jens Axboe
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=5e4904d5-e7fc-c079-e112-5b978c8fa129@kernel.dk \
--to=axboe@kernel.dk \
--cc=avi@scylladb.com \
--cc=glauber@scylladb.com \
--cc=io-uring@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.