From: syzbot <syzbot+listfdd86da488cce9cff3d4@syzkaller.appspotmail.com>
To: linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly hams report (Nov 2025)
Date: Tue, 25 Nov 2025 00:46:26 -0800 [thread overview]
Message-ID: <69256ce2.a70a0220.d98e3.00a0.GAE@google.com> (raw)
Hello hams maintainers/developers,
This is a 31-day syzbot report for the hams subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/hams
During the period, 1 new issues were detected and 0 were fixed.
In total, 10 issues are still open and 44 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9242 Yes possible deadlock in nr_rt_device_down (3)
https://syzkaller.appspot.com/bug?extid=ccdfb85a561b973219c7
<2> 2816 Yes possible deadlock in nr_rt_ioctl (2)
https://syzkaller.appspot.com/bug?extid=14afda08dc3484d5db82
<3> 660 Yes possible deadlock in nr_remove_neigh (2)
https://syzkaller.appspot.com/bug?extid=8863ad36d31449b4dc17
<4> 347 No WARNING: ODEBUG bug in __run_timers (3)
https://syzkaller.appspot.com/bug?extid=7287222a6d88bdb559a7
<5> 1 No WARNING: refcount bug in nr_del_neigh (2)
https://syzkaller.appspot.com/bug?extid=3f991c449d23d41216a2
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2025-11-25 8:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69256ce2.a70a0220.d98e3.00a0.GAE@google.com \
--to=syzbot+listfdd86da488cce9cff3d4@syzkaller.appspotmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.