From: syzbot <syzbot+5aca688dac0796c56129@syzkaller.appspotmail.com>
To: dhowells@redhat.com, ebiggers@kernel.org,
gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: WARNING in kfree
Date: Sun, 01 Sep 2019 07:06:00 -0700 [thread overview]
Message-ID: <000000000000e5f0e805917e5a60@google.com> (raw)
In-Reply-To: <0000000000003675ae05915a9fd3@google.com>
syzbot has bisected this bug to:
commit 3deadeebafcec6a0a7c9397bd32ea5ac6d5191c1
Author: David Howells <dhowells@redhat.com>
Date: Mon Jan 21 14:04:22 2019 +0000
vfs: Convert debugfs to use the new mount API
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=115d9e56600000
start commit: ed2393ca Add linux-next specific files for 20190827
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=135d9e56600000
console output: https://syzkaller.appspot.com/x/log.txt?x=155d9e56600000
kernel config: https://syzkaller.appspot.com/x/.config?x=2ef5940a07ed45f4
dashboard link: https://syzkaller.appspot.com/bug?extid=5aca688dac0796c56129
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1595ee12600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16df7fd2600000
Reported-by: syzbot+5aca688dac0796c56129@syzkaller.appspotmail.com
Fixes: 3deadeebafce ("vfs: Convert debugfs to use the new mount API")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-09-01 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 19:28 WARNING in kfree syzbot
2019-08-31 3:10 ` [PATCH vfs/for-next] vfs: fix vfs_get_single_reconf_super error handling Eric Biggers
2019-09-06 3:01 ` Eric Biggers
2019-09-01 14:06 ` 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=000000000000e5f0e805917e5a60@google.com \
--to=syzbot+5aca688dac0796c56129@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--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).