The stack trace looks to indicate a debugfs read triggering an out of bounds read against a kernel object backed by the slab. That is that the read is offset into the object such that the attempted read would have traversed onto the following object exposing kernel memory for an unrelated item. Do we know what the userspace application triggering this is actually doing when the fault triggers?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797367 Title: Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1797367/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
