From: patchwork-bot+netdevbpf@kernel.org
To: Sven Eckelmann <sven@narfation.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+ff3aa851d46ab82953a3@syzkaller.appspotmail.com,
syzbot+4036165fc595a74b09b2@syzkaller.appspotmail.com,
syzbot+c35d73ce910d86c0026e@syzkaller.appspotmail.com,
syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.com,
syzbot+f37372d86207b3bb2941@syzkaller.appspotmail.com
Subject: Re: [PATCH net v5] batman-adv: Fix double-hold of meshif when getting enabled
Date: Wed, 16 Apr 2025 03:10:34 +0000 [thread overview]
Message-ID: <174477303400.2860234.7904751019740013737.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250414-double_hold_fix-v5-1-10e056324cde@narfation.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Apr 2025 20:05:37 +0200 you wrote:
> It was originally meant to replace the dev_hold with netdev_hold. But this
> was missed in batadv_hardif_enable_interface(). As result, there was an
> imbalance and a hang when trying to remove the mesh-interface with
> (previously) active hard-interfaces:
>
> unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
>
> [...]
Here is the summary with links:
- [net,v5] batman-adv: Fix double-hold of meshif when getting enabled
https://git.kernel.org/netdev/net/c/10a77965760c
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:[~2025-04-16 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 18:05 [PATCH net v5] batman-adv: Fix double-hold of meshif when getting enabled Sven Eckelmann
2025-04-14 18:41 ` Eric Dumazet
2025-04-16 3: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=174477303400.2860234.7904751019740013737.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sven@narfation.org \
--cc=syzbot+4036165fc595a74b09b2@syzkaller.appspotmail.com \
--cc=syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.com \
--cc=syzbot+c35d73ce910d86c0026e@syzkaller.appspotmail.com \
--cc=syzbot+f37372d86207b3bb2941@syzkaller.appspotmail.com \
--cc=syzbot+ff3aa851d46ab82953a3@syzkaller.appspotmail.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