From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+989ff6506f5c6d1ff56b@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING: refcount bug in new_device_store
Date: Sat, 15 Aug 2026 08:07:14 +0800 [thread overview]
Message-ID: <20260815000715.1133-1-hdanton@sina.com> (raw)
In-Reply-To: <6a7ef6b0.10853dc7.22f513.0004.GAE@google.com>
> Date: Fri, 14 Aug 2026 04:06:24 -0700 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 2f1baf1fc892 Merge tag 'trace-v7.2-rc7' of git://git.kerne..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=170d8a25580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
> dashboard link: https://syzkaller.appspot.com/bug?extid=989ff6506f5c6d1ff56b
> compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=148d8a25580000
#syz test
--- x/drivers/net/netdevsim/bus.c
+++ y/drivers/net/netdevsim/bus.c
@@ -521,18 +521,18 @@ void nsim_bus_exit(void)
{
struct nsim_bus_dev *nsim_bus_dev, *tmp;
+ mutex_lock(&nsim_bus_dev_list_lock);
/* Disallow using resources */
smp_store_release(&nsim_bus_enable, false);
- if (refcount_dec_and_test(&nsim_bus_devs))
- complete(&nsim_bus_devs_released);
- mutex_lock(&nsim_bus_dev_list_lock);
list_for_each_entry_safe(nsim_bus_dev, tmp, &nsim_bus_dev_list, list) {
list_del(&nsim_bus_dev->list);
nsim_bus_dev_del(nsim_bus_dev);
}
mutex_unlock(&nsim_bus_dev_list_lock);
+ if (refcount_dec_and_test(&nsim_bus_devs))
+ complete(&nsim_bus_devs_released);
wait_for_completion(&nsim_bus_devs_released);
driver_unregister(&nsim_driver);
--
next prev parent reply other threads:[~2026-08-15 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 11:06 syzbot
2026-08-15 0:07 ` Hillf Danton [this message]
2026-08-15 0:22 ` syzbot
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=20260815000715.1133-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+989ff6506f5c6d1ff56b@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®