From: Wouter Verhelst
Date: Thu, 3 Sep 2020 14:05:15 +0200
> That's fine, because NBD doesn't deal with SOCK_DGRAM sockets anyway
> (i.e., passing a SOCK_DGRAM socket to the NBD device is undefined
> behavior).
Then why doesn't NBD simply reject such sockets?
Syzbot has reported those issues as:
==
BUG: KASAN: use-after-free in tipc_bcast_get_mode+0x3ab/0x400
net/tipc/bcast.c:759
Read of size 1 at addr 88805e6b3571 by task kworker/0:6/3850
CPU: 0 PID: 3850 Comm: kworker/0:6 Not
This reverts commit fdeba99b1e58ecd18c2940c453e19e4ef20ff591.
The commit caused to another deadlock as syzbot reported:
==
WARNING: possible circular locking dependency detected
5.9.0-rc2-next-20200828-syzkaller #0 Not tainted
