[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250407161308.19286-1-kuniyu@amazon.com>
Date: Mon, 7 Apr 2025 09:12:37 -0700
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <stfomichev@...il.com>
CC: <andrew@...n.ch>, <davem@...emloft.net>, <edumazet@...gle.com>,
<horms@...nel.org>, <kuba@...nel.org>, <kuniyu@...zon.com>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
<pabeni@...hat.com>, <sdf@...ichev.me>,
<syzbot+45016fe295243a7882d3@...kaller.appspotmail.com>,
<syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot] [net?] WARNING: bad unlock balance in do_setlink
From: Stanislav Fomichev <stfomichev@...il.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.
Powered by blists - more mailing lists