- 1. Re: INFO: task hung in stop_sync_thread (2) (score: 1)
- Author: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
- Date: Fri, 30 Mar 2018 18:54:33 +0200
- /\/\/\/\/\/\ now syzbot can test fixes -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger
- /html/lvs-devel/2018-03/msg00032.html (11,416 bytes)
- 2. Re: INFO: task hung in stop_sync_thread (2) (score: 1)
- Author: syzbot <syzbot+5fe074c01b2032ce9618@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Mar 2018 09:46:01 -0700
- syzbot has found reproducer for the following crash on net-next commit 18845557fd6fc1998f2d0d8c30467f86db587529 (Thu Mar 29 20:24:06 2018 +0000) Merge tag 'wireless-drivers-next-for-davem-2018-03-29'
- /html/lvs-devel/2018-03/msg00031.html (16,619 bytes)
- 3. Re: INFO: task hung in stop_sync_thread (2) (score: 1)
- Author: Julian Anastasov <ja@xxxxxx>
- Date: Thu, 29 Mar 2018 23:10:58 +0300 (EEST)
- Hello, I think, I know what happens: start_sync_thread holds rtnl_lock while calling kthread_stop on error. The backup kthread is signalled and it tries to rtnl_lock in sock_release => lockup. I thin
- /html/lvs-devel/2018-03/msg00030.html (20,238 bytes)
- 4. INFO: task hung in stop_sync_thread (2) (score: 1)
- Author: syzbot <syzbot+5fe074c01b2032ce9618@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Mar 2018 00:25:01 -0700
- Hello, syzbot hit the following crash on net-next commit 5d22d47b9ed96eddb35821dc2cc4f629f45827f7 (Tue Mar 27 17:33:21 2018 +0000) Merge branch 'sfc-filter-locking' syzbot dashboard link: https://syz
- /html/lvs-devel/2018-03/msg00029.html (19,052 bytes)
This search system is powered by
Namazu