From: Glauber Costa <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], Avi Kivity <[email protected]>,
Peter Zijlstra <[email protected]>
Subject: Re: Crash on using the poll ring
Date: Fri, 21 Feb 2020 14:51:06 -0500 [thread overview]
Message-ID: <CAD-J=zbKMHgnt+Tp0E5+hxt5BWP-uMuh1=HDCzcT8Aer9vhz+A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, Feb 21, 2020 at 2:04 PM Jens Axboe <[email protected]> wrote:
>
> On 2/21/20 7:51 AM, Jens Axboe wrote:
> > On 2/21/20 6:17 AM, Glauber Costa wrote:
> >> Hi
> >>
> >> Today I found a crash when adding code for the poll ring to my implementation.
> >> Kernel is 2b58a38ef46e91edd68eec58bdb817c42474cad6
> >>
> >> Here's how to reproduce:
> >>
> >> code at
> >> https://github.com/glommer/seastar.git branch poll-ring
> >>
> >> 1. same as previous steps to configure seastar, but compile with:
> >> ninja -C build/release apps/io_tester/io_tester
> >>
> >> 2. Download the yaml file attached
> >>
> >> 3. Run with:
> >>
> >> ./build/release/apps/io_tester/io_tester --conf ~/test.yaml --duration
> >> 15 --directory /var/disk1 --reactor-backend=uring --smp 1
> >>
> >> (directory must be on xfs because we do c++ but we're not savages)
> >
> > This is due to killing the dummy callback function on the task work.
> > I'll play with this a bit and see how we can fix it.
>
> I re-did the code to use task_works instead, can you try the current
> one? Same branch, sha is currently 9ba3cd1b8923.
Tnx. I don't see a crash any longer.
>
> --
> Jens Axboe
>
prev parent reply other threads:[~2020-02-21 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 13:17 Crash on using the poll ring Glauber Costa
2020-02-21 14:51 ` Jens Axboe
2020-02-21 19:04 ` Jens Axboe
2020-02-21 19:51 ` Glauber Costa [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 \
--in-reply-to='CAD-J=zbKMHgnt+Tp0E5+hxt5BWP-uMuh1=HDCzcT8Aer9vhz+A@mail.gmail.com' \
[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