From: Jens Axboe <axboe@kernel.dk>
To: Stephen Bates <sbates@raithlin.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: "fio-owner@vger.kernel.org" <fio-owner@vger.kernel.org>
Subject: Re: [io_uring]: fio's io_uring engine causing general protection fault
Date: Fri, 21 Jun 2019 10:23:24 -0600 [thread overview]
Message-ID: <561130eb-175b-7b34-2ba9-5e4cf7e60c54@kernel.dk> (raw)
In-Reply-To: <0EB5169E-C942-4974-8FEE-9F03B7574F36@raithlin.com>
On 6/21/19 9:15 AM, Stephen Bates wrote:
>> diff --git a/fs/io_uring.c b/fs/io_uring.c
>> index 86a2bd721900..485832deb7ea 100644
>
> Jens
>
> Thanks! I tested that and it seems to resolve the GPF. I now get a Bad
> file descriptor error in fio (which is I think what we'd expect). If
> you turn that patch into an official kernel patch feel free to add
Yep indeed, it's supposed to just result in an EBADF cqe. Thanks for
testing, I'll queue this up.
--
Jens Axboe
prev parent reply other threads:[~2019-06-21 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 12:40 [io_uring]: fio's io_uring engine causing general protection fault Stephen Bates
2019-06-21 13:13 ` Jens Axboe
2019-06-21 15:15 ` Stephen Bates
2019-06-21 16:23 ` 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 \
--in-reply-to=561130eb-175b-7b34-2ba9-5e4cf7e60c54@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio-owner@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=sbates@raithlin.com \
/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