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

Adam Conrad adconrad at 0c3.net
Thu Jun 16 07:58:26 UTC 2016


Hello Andy, or anyone else affected,

Accepted debian-installer into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu451.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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Changed in: debian-installer (Ubuntu Xenial)
       Status: In Progress => 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:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in s390-tools package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  Fix Committed
Status in s390-tools source package in Xenial:
  Fix Committed

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