From: syzbot <syzbot+33841dc6aa3e1d86b78a@syzkaller.appspotmail.com>
To: davem@davemloft.net, duoming@zju.edu.cn, edumazet@google.com,
jreuter@yaina.de, kuba@kernel.org, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, ralf@linux-mips.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hams?] WARNING: refcount bug in ax25_release (3)
Date: Tue, 25 Jun 2024 22:29:02 -0700 [thread overview]
Message-ID: <000000000000cc087d061bc44a72@google.com> (raw)
In-Reply-To: <0000000000009ce262061963e5e4@google.com>
syzbot has bisected this issue to:
commit 9fd75b66b8f68498454d685dc4ba13192ae069b0
Author: Duoming Zhou <duoming@zju.edu.cn>
Date: Fri Mar 18 00:54:04 2022 +0000
ax25: Fix refcount leaks caused by ax25_cb_del()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f83301980000
start commit: 568ebdaba637 MAINTAINERS: adjust file entry in FREESCALE Q..
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11f83301980000
console output: https://syzkaller.appspot.com/x/log.txt?x=16f83301980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e78fc116033e0ab7
dashboard link: https://syzkaller.appspot.com/bug?extid=33841dc6aa3e1d86b78a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=121324ae980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1607cdda980000
Reported-by: syzbot+33841dc6aa3e1d86b78a@syzkaller.appspotmail.com
Fixes: 9fd75b66b8f6 ("ax25: Fix refcount leaks caused by ax25_cb_del()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-26 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 23:38 [syzbot] [hams?] WARNING: refcount bug in ax25_release (3) syzbot
2024-06-24 22:37 ` syzbot
2024-06-26 5: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=000000000000cc087d061bc44a72@google.com \
--to=syzbot+33841dc6aa3e1d86b78a@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=edumazet@google.com \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@linux-mips.org \
--cc=syzkaller-bugs@googlegroups.com \
/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.