[Bug 1582728] Re: DASDFMT fails with a buffer overflow error

Dimitri John Ledkov launchpad at surgut.co.uk
Mon Jun 6 10:49:32 UTC 2016


** Description changed:

  [Impact]
  
-  * In certain hardware configurations, dasdfmt fails to format a drive,
+  * In certain hardware configurations, dasdfmt fails to format a drive,
  thus preventing successful installation and/or initialisation of a new
  disk.
  
  "there is a bug in the parsing of /proc/dasd/devices which is being
  triggered only if an FBA device is listed prior to the ECKD device in
  question. And since you've had FBA devices attached to your system
  during the installation, you ran into that bug."
  
  [Test Case]
  
-  * On a system with FBA and ECKD devices, perform dasdfmt
+  * Activate on a system and FBA device and a ECKD device
+  * Check that FBA device is listed first in /proc/dasd/devices
+  * Try to dasdfmt the ECKD device with $ dasdfmt -t /dev/dasdX
+  * One can change ECKD to "FBA " in /proc/dasd/devices by bind-mounting an edited file in place to reproduce the bug
  
  [Regression Potential]
  
-  * Minimal. Bug fix cherrypick from upstream.
+  * Minimal. Bug fix cherrypick from upstream.
  
  [Original Description]
-  
- During installation, either through the menu or in an ssh session , dasdfmt fails with a buffer overflow error and does not format the dasd volume. The volume is a z/VM minidisk - defined as 1 to end, this is common in this environment. The DASD volume was formatted from z/VM as a minidisk volume. These are the same steps taken for other distributions running under z/VM. I've attached some screen shots.
+ 
+ During installation, either through the menu or in an ssh session ,
+ dasdfmt fails with a buffer overflow error and does not format the dasd
+ volume. The volume is a z/VM minidisk - defined as 1 to end, this is
+ common in this environment. The DASD volume was formatted from z/VM as a
+ minidisk volume. These are the same steps taken for other distributions
+ running under z/VM. I've attached some screen shots.

** Changed in: s390-tools (Ubuntu)
       Status: Triaged => Fix Committed

-- 
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/1582728

Title:
  DASDFMT fails with a buffer overflow error

Status in Ubuntu on IBM z Systems:
  In Progress
Status in s390-tools package in Ubuntu:
  Fix Committed
Status in s390-tools source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * In certain hardware configurations, dasdfmt fails to format a
  drive, thus preventing successful installation and/or initialisation
  of a new disk.

  "there is a bug in the parsing of /proc/dasd/devices which is being
  triggered only if an FBA device is listed prior to the ECKD device in
  question. And since you've had FBA devices attached to your system
  during the installation, you ran into that bug."

  [Test Case]

   * Activate on a system and FBA device and a ECKD device
   * Check that FBA device is listed first in /proc/dasd/devices
   * Try to dasdfmt the ECKD device with $ dasdfmt -t /dev/dasdX
   * One can change ECKD to "FBA " in /proc/dasd/devices by bind-mounting an edited file in place to reproduce the bug

  [Regression Potential]

   * Minimal. Bug fix cherrypick from upstream.

  [Original Description]

  During installation, either through the menu or in an ssh session ,
  dasdfmt fails with a buffer overflow error and does not format the
  dasd volume. The volume is a z/VM minidisk - defined as 1 to end, this
  is common in this environment. The DASD volume was formatted from z/VM
  as a minidisk volume. These are the same steps taken for other
  distributions running under z/VM. I've attached some screen shots.

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



More information about the foundations-bugs mailing list