Re: Bluetooth/lock_sock: false positive "WARNING: possible recursive locking detected"

Hi Jiri, >> [ 2891.586061] >> [ 2891.586063] WARNING: possible recursive locking detected >> [ 2891.586065] 4.16.2-10.ge881e16-default #1 Not tainted >> [ 2891.586067] >> [ 28

Bluetooth/lock_sock: false positive "WARNING: possible recursive locking detected"

Hi, I have just got this lockdep warning during suspend: > [ 2891.586061] > [ 2891.586063] WARNING: possible recursive locking detected > [ 2891.586065] 4.16.2-10.ge881e16-default #1 Not tainted > [

Re: WARNING: possible recursive locking detected

t_sync_thread should be resolved soon... > > IPVS: sync thread started: state = BACKUP, mcast_ifn = lo, syncid = 0, id = > > 0 > > IPVS: stopping backup sync thread 4546 ... > > > > > > IPVS: stopping backup sync thread 4559 ... > > WARNING: possible recursive locking detected Regards -- Julian Anastasov

Re: WARNING: possible recursive locking detected

5) > IPVS: sync thread started: state = BACKUP, mcast_ifn = lo, syncid = 0, id = > 0 > IPVS: stopping backup sync thread 4546 ... > > ============ > IPVS: stopping backup sync thread 4559 ... > WARNING: possible recursive locking detected >

WARNING: possible recursive locking detected

ackup sync thread 4559 ... WARNING: possible recursive locking detected 4.16.0+ #19 Not tainted syzkaller046099/4543 is trying to acquire lock: 8d06d497 (rtnl_mutex){+.+.}, at: rtnl_lock+0x17/0x20 net/core/rtnetlink.c:74 but task is already ho