From: syzbot <syzbot+f70e9b00f8c7d4187bd0@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, darrick.wong@oracle.com,
davem@davemloft.net, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
netdev@vger.kernel.org, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: kernel BUG at lib/lockref.c:LINE!
Date: Mon, 08 Jul 2019 13:50:01 -0700 [thread overview]
Message-ID: <0000000000007c5b83058d3196cd@google.com> (raw)
In-Reply-To: <000000000000b519af058d3091d1@google.com>
syzbot has bisected this bug to:
commit 867c90eeea9d81ad1336881b61a4dcf692fc5d50
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon Jul 8 00:22:38 2019 +0000
Merge remote-tracking branch 'xfs/for-next'
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c69bc3a00000
start commit: d58b5ab9 Add linux-next specific files for 20190708
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=15c69bc3a00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11c69bc3a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=bf9882946ecc11d9
dashboard link: https://syzkaller.appspot.com/bug?extid=f70e9b00f8c7d4187bd0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=173375c7a00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1536f9bfa00000
Reported-by: syzbot+f70e9b00f8c7d4187bd0@syzkaller.appspotmail.com
Fixes: 867c90eeea9d ("Merge remote-tracking branch 'xfs/for-next'")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-07-08 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 19:37 kernel BUG at lib/lockref.c:LINE! syzbot
2019-07-08 20:29 ` Al Viro
2019-07-08 20:50 ` 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=0000000000007c5b83058d3196cd@google.com \
--to=syzbot+f70e9b00f8c7d4187bd0@syzkaller.appspotmail.com \
--cc=arvid.brodin@alten.se \
--cc=darrick.wong@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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.