Public bug reported:

---Problem Description---
In the zCX (Open Containers for z/OS), 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

** Affects: ubuntu-z-systems
     Importance: High
         Status: Incomplete

** Affects: s390-tools (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: Incomplete


** Tags: architecture-s39064 bugnameltc-174948 severity-high 
targetmilestone-inin1804

** Tags added: architecture-s39064 bugnameltc-174948 severity-high
targetmilestone-inin1804

** Changed in: ubuntu
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813888

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

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in s390-tools package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  In the zCX (Open Containers for z/OS), 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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to