All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+69a90a5e8f6b59086b2a@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hdanton@sina.com, josef@toxicpanda.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	mchristi@redhat.com, nbd@other.debian.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task can't die in nbd_ioctl
Date: Sat, 31 Oct 2020 05:43:05 -0700	[thread overview]
Message-ID: <000000000000bf140d05b2f6dae8@google.com> (raw)
In-Reply-To: <00000000000061316205b0e750fc@google.com>

syzbot has bisected this issue to:

commit e9e006f5fcf2bab59149cb38a48a4817c1b538b4
Author: Mike Christie <mchristi@redhat.com>
Date:   Sun Aug 4 19:10:06 2019 +0000

    nbd: fix max number of supported devs

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=154dc192500000
start commit:   4e78c578 Add linux-next specific files for 20201030
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=174dc192500000
console output: https://syzkaller.appspot.com/x/log.txt?x=134dc192500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=83318758268dc331
dashboard link: https://syzkaller.appspot.com/bug?extid=69a90a5e8f6b59086b2a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15e051a8500000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15bf75b8500000

Reported-by: syzbot+69a90a5e8f6b59086b2a@syzkaller.appspotmail.com
Fixes: e9e006f5fcf2 ("nbd: fix max number of supported devs")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2020-10-31 12:43 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
2020-11-13 12:10     ` Dmitry Vyukov
2020-11-13 16:28       ` syzbot
2020-10-31 12:43 ` 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=000000000000bf140d05b2f6dae8@google.com \
    --to=syzbot+69a90a5e8f6b59086b2a@syzkaller.appspotmail.com \
    --cc=axboe@kernel.dk \
    --cc=hdanton@sina.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchristi@redhat.com \
    --cc=nbd@other.debian.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.