From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+221cc24572a2fed23b6b@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, dan.j.williams@intel.com,
dhowells@redhat.com, gregkh@linuxfoundation.org,
hannes@cmpxchg.org, joel@joelfernandes.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab+samsung@kernel.org,
mingo@redhat.com, patrick.bellasi@arm.com, rgb@redhat.com,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, yamada.masahiro@socionext.com
Subject: Re: BUG: unable to handle kernel paging request in io_wq_cancel_all
Date: Wed, 30 Oct 2019 08:41:46 -0600 [thread overview]
Message-ID: <0e2bc2bf-2a7a-73c5-03e2-9d08f89f0ffa@kernel.dk> (raw)
In-Reply-To: <00000000000069801e05961be5fb@google.com>
On 10/30/19 1:44 AM, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit ef0524d3654628ead811f328af0a4a2953a8310f
> Author: Jens Axboe <axboe@kernel.dk>
> Date: Thu Oct 24 13:25:42 2019 +0000
>
> io_uring: replace workqueue usage with io-wq
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16acf5d0e00000
> start commit: c57cf383 Add linux-next specific files for 20191029
> git tree: linux-next
> final crash: https://syzkaller.appspot.com/x/report.txt?x=15acf5d0e00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=11acf5d0e00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=cb86688f30db053d
> dashboard link: https://syzkaller.appspot.com/bug?extid=221cc24572a2fed23b6b
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=168671d4e00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=140f4898e00000
>
> Reported-by: syzbot+221cc24572a2fed23b6b@syzkaller.appspotmail.com
> Fixes: ef0524d36546 ("io_uring: replace workqueue usage with io-wq")
Good catch, it's a case of NULL vs ERR_PTR() confusion. I'll fold in
the below fix.
diff --git a/fs/io_uring.c b/fs/io_uring.c
index af1937d66aee..76d653085987 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -3534,8 +3534,9 @@ static int io_sq_offload_start(struct io_ring_ctx *ctx,
/* Do QD, or 4 * CPUS, whatever is smallest */
concurrency = min(ctx->sq_entries, 4 * num_online_cpus());
ctx->io_wq = io_wq_create(concurrency, ctx->sqo_mm);
- if (!ctx->io_wq) {
- ret = -ENOMEM;
+ if (IS_ERR(ctx->io_wq)) {
+ ret = PTR_ERR(ctx->io_wq);
+ ctx->io_wq = NULL;
goto err;
}
--
Jens Axboe
next prev parent reply other threads:[~2019-10-30 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 5:32 BUG: unable to handle kernel paging request in io_wq_cancel_all syzbot
2019-10-30 7:44 ` syzbot
2019-10-30 14:41 ` Jens Axboe [this message]
2019-11-01 17:50 ` Dmitry Vyukov
2019-11-01 17:56 ` Jens Axboe
2019-11-01 18:03 ` Dmitry Vyukov
2019-11-01 18:07 ` 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=0e2bc2bf-2a7a-73c5-03e2-9d08f89f0ffa@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=joel@joelfernandes.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@arm.com \
--cc=rgb@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzbot+221cc24572a2fed23b6b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yamada.masahiro@socionext.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