From: syzbot <syzbot+9c69c282adc4edd2b540@syzkaller.appspotmail.com>
To: amir73il@gmail.com, dvyukov@google.com,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, mszeredi@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in ovl_instantiate
Date: Tue, 26 Mar 2019 05:10:00 -0700 [thread overview]
Message-ID: <0000000000004f7f7c0584fe33c0@google.com> (raw)
In-Reply-To: <000000000000064bcf057a59e3b9@google.com>
syzbot has bisected this bug to:
commit 01b39dcc95680b04c7af5de7f39f577e9c4865e3
Author: Amir Goldstein <amir73il@gmail.com>
Date: Fri May 11 08:15:15 2018 +0000
ovl: use inode_insert5() to hash a newly created inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=176da0cd200000
start commit: de6629eb Merge tag 'pci-v5.0-fixes-1' of git://git.kernel...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=14eda0cd200000
console output: https://syzkaller.appspot.com/x/log.txt?x=10eda0cd200000
kernel config: https://syzkaller.appspot.com/x/.config?x=edf1c3031097c304
dashboard link: https://syzkaller.appspot.com/bug?extid=9c69c282adc4edd2b540
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c7a94f400000
Reported-by: syzbot+9c69c282adc4edd2b540@syzkaller.appspotmail.com
Fixes: 01b39dcc9568 ("ovl: use inode_insert5() to hash a newly created
inode")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-26 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 1:56 WARNING in ovl_instantiate syzbot
2018-12-15 19:34 ` syzbot
2018-12-16 17:00 ` Amir Goldstein
2018-12-17 10:46 ` Dmitry Vyukov
2018-12-17 13:30 ` Amir Goldstein
2018-12-18 14:12 ` Dmitry Vyukov
2019-03-26 12:10 ` syzbot [this message]
2019-04-19 8:21 ` Amir Goldstein
2019-04-19 8:52 ` syzbot
2019-04-19 8:53 ` syzbot
2019-04-22 10:12 ` Dmitry Vyukov
2019-04-22 11:08 ` Amir Goldstein
2019-04-22 11:58 ` Dmitry Vyukov
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=0000000000004f7f7c0584fe33c0@google.com \
--to=syzbot+9c69c282adc4edd2b540@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.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).