From: syzbot <syzbot+5fa698422954b6b9307b@syzkaller.appspotmail.com>
To: axboe@kernel.dk, balbi@kernel.org, corbet@lwn.net,
gregkh@linuxfoundation.org, linux-block@vger.kernel.org,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
lorenzo@google.com, manish.narani@xilinx.com, maze@google.com,
netdev@vger.kernel.org, phind.uet@gmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: invalid-free in bdev_free_inode (2)
Date: Fri, 20 Aug 2021 19:29:06 -0700 [thread overview]
Message-ID: <000000000000552aaf05ca088c20@google.com> (raw)
In-Reply-To: <00000000000000410c05c8e29289@google.com>
syzbot has bisected this issue to:
commit 63d152149b2d0860ccf8c4e6596b6175b2b7ace6
Author: Lorenzo Colitti <lorenzo@google.com>
Date: Wed Jan 13 23:42:22 2021 +0000
usb: gadget: u_ether: support configuring interface names.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155abcc1300000
start commit: d3432bf10f17 net: Support filtering interfaces on no master
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=175abcc1300000
console output: https://syzkaller.appspot.com/x/log.txt?x=135abcc1300000
kernel config: https://syzkaller.appspot.com/x/.config?x=8075b2614f3db143
dashboard link: https://syzkaller.appspot.com/bug?extid=5fa698422954b6b9307b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=174ebaf6300000
Reported-by: syzbot+5fa698422954b6b9307b@syzkaller.appspotmail.com
Fixes: 63d152149b2d ("usb: gadget: u_ether: support configuring interface names.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-08-21 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 11:45 [syzbot] KASAN: invalid-free in bdev_free_inode (2) syzbot
2021-08-11 11:16 ` syzbot
2021-08-21 2:29 ` 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=000000000000552aaf05ca088c20@google.com \
--to=syzbot+5fa698422954b6b9307b@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=balbi@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=manish.narani@xilinx.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=phind.uet@gmail.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 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).