All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+45016fe295243a7882d3@syzkaller.appspotmail.com>
To: 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,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING: bad unlock balance in do_setlink
Date: Mon, 07 Apr 2025 01:13:03 -0700	[thread overview]
Message-ID: <67f3890f.050a0220.0a13.0286.GAE@google.com> (raw)
In-Reply-To: <20250407063703.20757-1-kuniyu@amazon.com>

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


Tested on:

commit:         61f96e68 Merge tag 'net-6.15-rc1' of git://git.kernel...
git tree:       net
console output: https://syzkaller.appspot.com/x/log.txt?x=111c523f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f2054704dd53fb80
dashboard link: https://syzkaller.appspot.com/bug?extid=45016fe295243a7882d3
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=12f3bd98580000


  reply	other threads:[~2025-04-07  8: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 [this message]
2025-04-07 14:19     ` Stanislav Fomichev
2025-04-07 16:12       ` Kuniyuki Iwashima
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=67f3890f.050a0220.0a13.0286.GAE@google.com \
    --to=syzbot+45016fe295243a7882d3@syzkaller.appspotmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.