From: Ming Lei <tom.leiming@gmail.com>
To: syzbot <syzbot+69a90a5e8f6b59086b2a@syzkaller.appspotmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, Josef Bacik <josef@toxicpanda.com>,
linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
nbd@other.debian.org, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task can't die in nbd_ioctl
Date: Tue, 3 Nov 2020 15:21:40 +0800 [thread overview]
Message-ID: <CACVXFVNk9Os+2Bzht+eoeFZr=E-FCBZg2SSYx5AP_eu_-3zF3w@mail.gmail.com> (raw)
In-Reply-To: <0000000000004cb88b05b2e8d1b4@google.com>
On Sat, Oct 31, 2020 at 4:01 AM syzbot
<syzbot+69a90a5e8f6b59086b2a@syzkaller.appspotmail.com> wrote:
>
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 4e78c578 Add linux-next specific files for 20201030
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=158c1798500000
> kernel config: https://syzkaller.appspot.com/x/.config?x=83318758268dc331
> dashboard link: https://syzkaller.appspot.com/bug?extid=69a90a5e8f6b59086b2a
> compiler: gcc (GCC) 10.1.0-syz 20200507
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15e051a8500000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15bf75b8500000
Not reproduce this issue by above C reproducer with the kernel config
in hours running
on linus tree.
Thanks,
Ming Lei
next prev parent reply other threads:[~2020-11-03 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 7:20 INFO: task can't die in nbd_ioctl syzbot
2020-10-30 19:58 ` syzbot
2020-11-03 7:21 ` Ming Lei [this message]
2020-11-13 12:10 ` Dmitry Vyukov
2020-11-13 16:28 ` syzbot
2020-10-31 12:43 ` syzbot
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='CACVXFVNk9Os+2Bzht+eoeFZr=E-FCBZg2SSYx5AP_eu_-3zF3w@mail.gmail.com' \
--to=tom.leiming@gmail.com \
--cc=axboe@kernel.dk \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=syzbot+69a90a5e8f6b59086b2a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).