From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: WARNING: bad unlock balance in mptcp_shutdown
Date: Sun, 12 Apr 2020 00:43:37 +0200 [thread overview]
Message-ID: <20200411224337.GA5795@breakpoint.cc> (raw)
In-Reply-To: 000000000000adb83a05a30aaa04@google.com
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
> console output: https://syzkaller.appspot.com/x/log.txt?x=17a5dbfbe00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ca75979eeebf06c2
> dashboard link: https://syzkaller.appspot.com/bug?extid=6ebb6d4830e8f8815623
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+6ebb6d4830e8f8815623(a)syzkaller.appspotmail.com
>
> =====================================
> WARNING: bad unlock balance detected!
> 5.6.0-syzkaller #0 Not tainted
> -------------------------------------
> syz-executor.5/2215 is trying to release lock (sk_lock-AF_INET6) at:
> [<ffffffff87c5203b>] mptcp_shutdown+0x38b/0x550 net/mptcp/protocol.c:1889
> but there are no more locks to release!
>
> other info that might help us debug this:
> 1 lock held by syz-executor.5/2215:
> #0: ffff88804a22eda0 (slock-AF_INET6){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:358 [inline]
> #0: ffff88804a22eda0 (slock-AF_INET6){+.-.}-{2:2}, at: release_sock+0x1b/0x1b0 net/core/sock.c:2974
I think this is same issue as the other report, so:
#syz dup: WARNING: bad unlock balance in mptcp_poll
WARNING: multiple messages have this Message-ID (diff)
From: Florian Westphal <fw@strlen.de>
To: syzbot <syzbot+6ebb6d4830e8f8815623@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, mathew.j.martineau@linux.intel.com,
matthieu.baerts@tessares.net, mptcp@lists.01.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [MPTCP] WARNING: bad unlock balance in mptcp_shutdown
Date: Sun, 12 Apr 2020 00:43:37 +0200 [thread overview]
Message-ID: <20200411224337.GA5795@breakpoint.cc> (raw)
In-Reply-To: <000000000000adb83a05a30aaa04@google.com>
> console output: https://syzkaller.appspot.com/x/log.txt?x=17a5dbfbe00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ca75979eeebf06c2
> dashboard link: https://syzkaller.appspot.com/bug?extid=6ebb6d4830e8f8815623
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+6ebb6d4830e8f8815623@syzkaller.appspotmail.com
>
> =====================================
> WARNING: bad unlock balance detected!
> 5.6.0-syzkaller #0 Not tainted
> -------------------------------------
> syz-executor.5/2215 is trying to release lock (sk_lock-AF_INET6) at:
> [<ffffffff87c5203b>] mptcp_shutdown+0x38b/0x550 net/mptcp/protocol.c:1889
> but there are no more locks to release!
>
> other info that might help us debug this:
> 1 lock held by syz-executor.5/2215:
> #0: ffff88804a22eda0 (slock-AF_INET6){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:358 [inline]
> #0: ffff88804a22eda0 (slock-AF_INET6){+.-.}-{2:2}, at: release_sock+0x1b/0x1b0 net/core/sock.c:2974
I think this is same issue as the other report, so:
#syz dup: WARNING: bad unlock balance in mptcp_poll
next reply other threads:[~2020-04-11 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 22:43 Florian Westphal [this message]
2020-04-11 22:43 ` [MPTCP] WARNING: bad unlock balance in mptcp_shutdown Florian Westphal
-- strict thread matches above, loose matches on Subject: below --
2020-04-12 3:29 [MPTCP] " Hillf Danton
2020-04-11 21:38 [MPTCP] " syzbot
2020-04-11 21:38 ` syzbot
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=20200411224337.GA5795@breakpoint.cc \
--to=unknown@example.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.