Re: WARNING: possible recursive locking detected

2018-04-11 Thread Julian Anastasov
tree, so all these lockups around start_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 <j...@ssi.bg>

Re: WARNING: possible recursive locking detected

2018-04-11 Thread Julian Anastasov
ead 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

2018-04-11 Thread Dmitry Vyukov
footer. #syz dup: possible deadlock in rtnl_lock (5) > IPVS: sync thread started: state = BACKUP, mcast_ifn = lo, syncid = 0, id = > 0 > IPVS: stopping backup sync thread 4546 ... > > ================ > IPVS: stopping backup

Re: WARNING: possible recursive locking detected

2018-04-11 Thread Dmitry Vyukov
PVS: 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 > 4.16.0+ #1

WARNING: possible recursive locking detected

2018-04-11 Thread syzbot
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 holding lock

WARNING: possible recursive locking detected

2018-04-11 Thread syzbot
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 holding lock

WARNING: possible recursive locking detected on linux-next

2017-05-18 Thread Corentin Labbe
Hello Since linux-next-20170516 I got the following warning trace: [4.310450] nf_tables: (c) 2007-2009 Patrick McHardy <ka...@trash.net> [4.321211] [4.326516] WARNING: possible recursive locking detected [4.331823] 4.12.0-rc

WARNING: possible recursive locking detected on linux-next

2017-05-18 Thread Corentin Labbe
Hello Since linux-next-20170516 I got the following warning trace: [4.310450] nf_tables: (c) 2007-2009 Patrick McHardy [4.321211] [4.326516] WARNING: possible recursive locking detected [4.331823] 4.12.0-rc1-next-20170518+ #274