From: patchwork-bot+netdevbpf@kernel.org
To: Adriano Cordova <adrianox@gmail.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org,
syzbot+989ff6506f5c6d1ff56b@syzkaller.appspot.com
Subject: Re: [PATCH net v2] netdevsim: take bus device refcount before registering device
Date: Fri, 04 Sep 2026 00:10:12 +0000 [thread overview]
Message-ID: <178848061288.4080441.9633200438937067830.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260902025704.34606-1-adrianox@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Sep 2026 22:57:04 -0400 you wrote:
> nsim_bus_dev_release() drops nsim_bus_devs when a device is freed, but
> the matching increment was done in new_device_store() after
> nsim_bus_dev_new() returned. When device_register() failed inside
> nsim_bus_dev_new(), put_device() invoked the release callback and
> decremented without an increment, driving the refcount to zero; a later
> creation then incremented from zero (refcount_t: addition on 0).
>
> [...]
Here is the summary with links:
- [net,v2] netdevsim: take bus device refcount before registering device
https://git.kernel.org/netdev/net-next/c/d5f5853f167f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-04 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 2:57 [PATCH net v2] netdevsim: take bus device refcount before registering device Adriano Cordova
2026-09-04 0:10 ` patchwork-bot+netdevbpf [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=178848061288.4080441.9633200438937067830.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=adrianox@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+989ff6506f5c6d1ff56b@syzkaller.appspot.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