** Description changed: + [Impact] + + * lsqeth core dumps on systems without any qeth devices, as called from + sosreport + + [Test Case] + + * lsqeth should not fail on networkless machines + + [Regression Potential] + + * cherrypicked upstream patches, tested upstream & disco + * changes to the unusual code path, of absent devices for otherwise typically only networked installs + + [Other Info] + + * Original bug report + ---Problem Description--- We run in an environment where we have no eth devices defined and therefore no /sys/bus/ccwgroup exists. We are experiencing intermittent problems with a segmentation fault in the lsqeth program. In particular when called from sosreport it consistently fails but if invoking directly from the command line, it most likely does not cause an error. We found out that the logic of lsqeth from s390-tools always expect the directory '/sys/bus/ccwgroup/drivers/qeth/' to be existed. And it doesn't handle the scenario if the directory doesn't exist and causes the core dump in our case. IBM willl provide an upstream patch for s390tools once available. This package upgrade need to released by Bionic as soon as possible. ---uname output--- 4.15.0-42-generic Machine Type = system Z ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. run in an environment with no eth devices defined and therefore no /sys/bus/ccwgroup exists. 2. timeout 10 lsqeth
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813888 Title: [Ubuntu] lsqeth core dumps when called from sosreport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1813888/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
