From: syzbot <syzbot+032bc63605089a199d30@syzkaller.appspotmail.com>
To: amir73il@gmail.com, bfields@fieldses.org, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: WARNING in ovl_real_fdget_meta
Date: Wed, 24 Jul 2019 21:24:00 -0700 [thread overview]
Message-ID: <00000000000086c732058e79cb59@google.com> (raw)
In-Reply-To: <0000000000004a3a63058e722b94@google.com>
syzbot has bisected this bug to:
commit 387e3746d01c34457d6a73688acd90428725070b
Author: Amir Goldstein <amir73il@gmail.com>
Date: Fri Jun 7 14:24:38 2019 +0000
locks: eliminate false positive conflicts for write lease
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a79594600000
start commit: c6dd78fc Merge branch 'x86-urgent-for-linus' of git://git...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17a79594600000
console output: https://syzkaller.appspot.com/x/log.txt?x=13a79594600000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c8985c08e1f9727
dashboard link: https://syzkaller.appspot.com/bug?extid=032bc63605089a199d30
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15855334600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17fcc4c8600000
Reported-by: syzbot+032bc63605089a199d30@syzkaller.appspotmail.com
Fixes: 387e3746d01c ("locks: eliminate false positive conflicts for write
lease")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-07-25 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000004a3a63058e722b94@google.com>
2019-07-25 4:24 ` syzbot [this message]
2019-07-26 8:11 ` WARNING in ovl_real_fdget_meta Amir Goldstein
2019-07-26 10:06 ` Amir Goldstein
2019-07-26 16:31 ` Amir Goldstein
2019-07-27 2:41 ` 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=00000000000086c732058e79cb59@google.com \
--to=syzbot+032bc63605089a199d30@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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 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).