BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 46s!
BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 45s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
  pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=2/256
    in-flight: 1979:cache_reap
    pending: iterate_cleanup_work
  pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=7/256
    pending: defense_work_handler, defense_work_handler, defense_work_handler, defense_work_handler, defense_work_handler, vmstat_shepherd, cache_reap
workqueue events_unbound: flags=0x2
  pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/512
    in-flight: 6677:fsnotify_mark_destroy_workfn
workqueue events_power_efficient: flags=0x80
  pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=2/256
    pending: neigh_periodic_work, neigh_periodic_work
workqueue rcu_gp: flags=0x8
  pwq 2: cpus=1 node=0 flags=0x0 nice=0 active=1/256
    pending: srcu_invoke_callbacks
workqueue mm_percpu_wq: flags=0x8
  pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
    pending: vmstat_update
workqueue writeback: flags=0x4e
  pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/256
    pending: wb_workfn
workqueue ib_addr: flags=0xa0002
  pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/1
    pending: process_req
workqueue gid-cache-wq: flags=0xa0002
  pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/1
    pending: update_gid_event_work_handler
workqueue dm_bufio_cache: flags=0x8
  pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
    pending: work_fn
workqueue krdsd: flags=0xe000a
  pwq 4: cpus=0-1 flags=0x4 nice=0 active=1/1
    pending: rds_connect_worker
pool 2: cpus=1 node=0 flags=0x0 nice=0 hung=0s workers=4 idle: 24 2106 18
pool 4: cpus=0-1 flags=0x4 nice=0 hung=0s workers=7 idle: 62 22 6 7154 143 6679
bridge0: port 2(bridge_slave_1) entered disabled state
bridge0: port 1(bridge_slave_0) entered disabled state
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered forwarding state
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered forwarding state
device bridge0 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): bridge0: link is not ready
sock: process `syz-executor6' is using obsolete setsockopt SO_BSDCOMPAT
bridge0: port 2(bridge_slave_1) entered disabled state
bridge0: port 1(bridge_slave_0) entered disabled state
device bridge0 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered blocking state
bridge0: port 2(bridge_slave_1) entered forwarding state
bridge0: port 1(bridge_slave_0) entered blocking state
bridge0: port 1(bridge_slave_0) entered forwarding state
device bridge0 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): bridge0: link is not ready
netlink: 12 bytes leftover after parsing attributes in process `syz-executor0'.
netlink: 12 bytes leftover after parsing attributes in process `syz-executor0'.
xt_CONNSECMARK: only valid in 'mangle' or 'security' table, not 'broute'
xt_CONNSECMARK: only valid in 'mangle' or 'security' table, not 'broute'
IPv6: ADDRCONF(NETDEV_CHANGE): bridge0: link becomes ready
openvswitch: netlink: Flow key attr not present in new flow.
openvswitch: netlink: Flow key attr not present in new flow.
kernel msg: ebtables bug: please report to author: Wrong len argument
kernel msg: ebtables bug: please report to author: Wrong len argument
syz-executor3 (20968) used greatest stack depth: 11416 bytes left
netlink: 8 bytes leftover after parsing attributes in process `syz-executor5'.
netlink: 8 bytes leftover after parsing attributes in process `syz-executor5'.
netlink: 20 bytes leftover after parsing attributes in process `syz-executor1'.