From: syzbot <syzbot+83e12cf81d2c14842146@syzkaller.appspotmail.com>
To: bfields@fieldses.org, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
neilb@suse.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: general protection fault in __x86_indirect_thunk_rbx
Date: Wed, 20 Mar 2019 22:32:00 -0700 [thread overview]
Message-ID: <000000000000b3976c0584940e6e@google.com> (raw)
In-Reply-To: <00000000000089d2c9057a0c083a@google.com>
syzbot has bisected this bug to:
commit dee160df820de41ff2f59a715643680822a0ab06
Author: NeilBrown <neilb@suse.com>
Date: Mon Nov 5 01:30:47 2018 +0000
locks: use properly initialized file_lock when unlocking.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd7200000
start commit: dee160df locks: use properly initialized file_lock when un..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=100b9fd7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17f39fd7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437
dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd9447400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000
Reported-by: syzbot+83e12cf81d2c14842146@syzkaller.appspotmail.com
Fixes: dee160df ("locks: use properly initialized file_lock when
unlocking.")
next prev parent reply other threads:[~2019-03-21 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 5:03 general protection fault in __x86_indirect_thunk_rbx syzbot
2018-11-07 7:47 ` syzbot
2019-03-21 5:32 ` syzbot [this message]
2019-03-21 6:07 ` NeilBrown
2019-03-21 6:16 ` 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=000000000000b3976c0584940e6e@google.com \
--to=syzbot+83e12cf81d2c14842146@syzkaller.appspotmail.com \
--cc=bfields@fieldses.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--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.