From: syzbot <syzbot+2f8fa4e860edc3066aba@syzkaller.appspotmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: axboe@kernel.dk, io-uring@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: Re: possible deadlock in io_write
Date: Mon, 28 Sep 2020 08:01:22 -0700 [thread overview]
Message-ID: <00000000000086c59505b060f073@google.com> (raw)
In-Reply-To: <69d85830-b846-72ad-7315-545509f3a099@kernel.dk>
> Not the prettiest solution, but I don't think that's a real concern as
> this is just for human consumption.
>
> #syz test: git://git.kernel.dk/linux-block io_uring-5.9
This crash does not have a reproducer. I cannot test it.
>
> --
> Jens Axboe
>
prev parent reply other threads:[~2020-09-28 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:17 possible deadlock in io_write syzbot
2020-09-28 15:01 ` Jens Axboe
2020-09-28 15:01 ` syzbot [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=00000000000086c59505b060f073@google.com \
--to=syzbot+2f8fa4e860edc3066aba@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).