------- Comment From dougm...@us.ibm.com 2018-04-24 11:06 EDT------- I'm not up to speed on the double-free issue, but if multiple work queues/pools referenced the same work item, you could get a double free situation. Essentially, the qla2xxx driver doing the double (triple, ...) insertion of a work item on multiple pools could result in addition work items, appended to that fatal qla2xxx item, getting executed on multiple kworker threads. So, it is possible that the skb-related failures were an odd case where some network work item was unlucky enough to get appended to one of these offending qla2xxx items, and we saw collateral damage (panics) as a result. If that unlucky work item were dynamically allocated, it could get freed multiple times.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762844 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1762844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
