From: syzbot <syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com>
To: broonie@kernel.org, davem@davemloft.net, edumazet@google.com,
groeck@chromium.org, jiri@resnulli.us, kuba@kernel.org,
linmq006@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
tzungbi@kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [net?] WARNING in print_bfs_bug (2)
Date: Sat, 29 Apr 2023 15:54:28 -0700 [thread overview]
Message-ID: <000000000000db8c6605fa8178df@google.com> (raw)
In-Reply-To: <000000000000e5ee7305f0f975e8@google.com>
syzbot has bisected this issue to:
commit 0a034d93ee929a9ea89f3fa5f1d8492435b9ee6e
Author: Miaoqian Lin <linmq006@gmail.com>
Date: Fri Jun 3 13:10:43 2022 +0000
ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d40608280000
start commit: 042334a8d424 atlantic:hw_atl2:hw_atl2_utils_fw: Remove unn..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10340608280000
console output: https://syzkaller.appspot.com/x/log.txt?x=17d40608280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7205cdba522fe4bc
dashboard link: https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=147328f8280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1665151c280000
Reported-by: syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com
Fixes: 0a034d93ee92 ("ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2023-04-29 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e5ee7305f0f975e8@google.com>
2023-04-29 22:54 ` syzbot [this message]
2023-05-03 2:49 ` [syzbot] [net?] WARNING in print_bfs_bug (2) Tzung-Bi Shih
2023-05-05 13:27 ` Mark Brown
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=000000000000db8c6605fa8178df@google.com \
--to=syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=groeck@chromium.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tzungbi@kernel.org \
--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).