From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <stfomichev@gmail.com>
Cc: <andrew@lunn.ch>, <davem@davemloft.net>, <edumazet@google.com>,
<horms@kernel.org>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>, <sdf@fomichev.me>,
<syzbot+45016fe295243a7882d3@syzkaller.appspotmail.com>,
<syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] [net?] WARNING: bad unlock balance in do_setlink
Date: Mon, 7 Apr 2025 09:12:37 -0700 [thread overview]
Message-ID: <20250407161308.19286-1-kuniyu@amazon.com> (raw)
In-Reply-To: <Z_PfCosPB7GS4DJl@mini-arch>
From: Stanislav Fomichev <stfomichev@gmail.com>
Date: Mon, 7 Apr 2025 07:19:54 -0700
> On 04/07, syzbot wrote:
> > Hello,
> >
> > syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> > unregister_netdevice: waiting for DEV to become free
> >
> > unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
>
> So it does fix the lock unbalance issue, but now there is a hang?
I think this is an orthogonal issue.
I saw this in another report as well.
https://lore.kernel.org/netdev/67f208ea.050a0220.0a13.025b.GAE@google.com/
syzbot may want to find a better way to filter this kind of noise.
next prev parent reply other threads:[~2025-04-07 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 5:57 [syzbot] [net?] WARNING: bad unlock balance in do_setlink syzbot
2025-04-07 6:37 ` Kuniyuki Iwashima
2025-04-07 8:13 ` syzbot
2025-04-07 14:19 ` Stanislav Fomichev
2025-04-07 16:12 ` Kuniyuki Iwashima [this message]
2025-04-08 8:11 ` Aleksandr Nogikh
2025-04-08 10:44 ` Dmitry Vyukov
2025-04-08 11:33 ` Eric Dumazet
2025-04-08 20:16 ` Aleksandr Nogikh
2025-04-08 20:41 ` Eric Dumazet
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=20250407161308.19286-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=andrew@lunn.ch \
--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=sdf@fomichev.me \
--cc=stfomichev@gmail.com \
--cc=syzbot+45016fe295243a7882d3@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;
as well as URLs for NNTP newsgroup(s).