[Bug 1813888] Re: [Ubuntu] lsqeth core dumps when called from sosreport

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted s390-tools into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.6.0-0ubuntu7.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: s390-tools (Ubuntu Cosmic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to s390-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1813888

Title:
  [Ubuntu] lsqeth core dumps when called from sosreport

Status in Ubuntu on IBM z Systems:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Released
Status in s390-tools source package in Bionic:
  In Progress
Status in s390-tools source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * lsqeth core dumps on systems without any qeth devices, as called
  from sosreport

  [Test Case]

   * lsqeth should not fail on networkless machines

  * create a z/vm or lpar, and do not add any qeth ethernet adaptors (no
  network cards)

  * use serial terminal to execute `lsqeth` -> to list available
  ethernet cards, when there are none at all

  * expectation is that the binary exits listing nothing, without
  crashing/sigaborting.

  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1813888/+subscriptions