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

[Dimitri John Ledkov]

** Description changed:

  [Impact]
  
-  * lsqeth core dumps on systems without any qeth devices, as called from
+  * lsqeth core dumps on systems without any qeth devices, as called from
  sosreport
  
  [Test Case]
  
-  * lsqeth should not fail on networkless machines
+  * 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
+  * 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
+ 
+  * 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
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:
  In Progress

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