From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
io-uring <[email protected]>
Subject: Re: [BUG] io_uring
Date: Fri, 17 Jan 2020 15:52:12 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/17/20 3:05 PM, Pavel Begunkov wrote:
> I'm hitting a bug with yesterday's for-next (e.g. 126c20adbd98f2eff00c837afc).
> I'll debug it in several days, if nobody would do it by then.
>
> kernel: yesterday's for-next (e.g. 126c20adbd98f2eff00c837afc)
> How to reproduce: run ./file-update in a loop (for me 10th run hit the problem)
Let me know if it still happens in the current tree, I fixed the wait on this.
But it might be something new, we'll see.
--
Jens Axboe
prev parent reply other threads:[~2020-01-17 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 22:05 [BUG] io_uring Pavel Begunkov
2020-01-17 22:52 ` 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] \
/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