LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: syzbot <syzbot+3337db851ace689ceb50@syzkaller.appspotmail.com>
To: akinobu.mita@gmail.com, akpm@linux-foundation.org,
	axboe@kernel.dk, dvyukov@google.com, gregkh@linuxfoundation.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	mhocko@kernel.org, syzkaller-bugs@googlegroups.com,
	torvalds@linux-foundation.org
Subject: Re: WARNING in __device_add_disk
Date: Tue, 26 Nov 2019 02:16:01 -0800	[thread overview]
Message-ID: <000000000000c5f3d905983d2ae0@google.com> (raw)
In-Reply-To: <0000000000001558f3056a369689@google.com>

syzbot has bisected this bug to:

commit e41d58185f1444368873d4d7422f7664a68be61d
Author: Dmitry Vyukov <dvyukov@google.com>
Date:   Wed Jul 12 21:34:35 2017 +0000

     fault-inject: support systematic fault injection

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17889f5ae00000
start commit:   6da6c0db Linux v4.17-rc3
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=14489f5ae00000
console output: https://syzkaller.appspot.com/x/log.txt?x=10489f5ae00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5a1dc06635c10d27
dashboard link: https://syzkaller.appspot.com/bug?extid=3337db851ace689ceb50
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15191837800000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=120af5c7800000

Reported-by: syzbot+3337db851ace689ceb50@syzkaller.appspotmail.com
Fixes: e41d58185f14 ("fault-inject: support systematic fault injection")

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

      parent reply	other threads:[~2019-11-26 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 17:06 syzbot
2018-04-30 12:37 ` syzbot
2019-11-26 10:16 ` 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=000000000000c5f3d905983d2ae0@google.com \
    --to=syzbot+3337db851ace689ceb50@syzkaller.appspotmail.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=dvyukov@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: WARNING in __device_add_disk' \
    /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

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).