[Bug 1800867] Re: [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding - s390tools part

[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.1 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/1800867

Title:
  [18.10 FEAT] zcrypt DD: introduce APQN tags to support deterministic
  driver binding - s390tools part

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:
  New
Status in s390-tools source package in Cosmic:
  Fix Committed
Status in s390-tools source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * HW enablement
   * Kernel supports alternate zcrypt device drivers, hence lszcrypt (an information tool) should show if a driver is bound, and which one, given that it is no longer unambiguous.

  [Test Case]

   * Run lszcrypt, ensure it shows info about crypto cards, and a driver
  name.

  $ lszcrypt -V
  CARD.DOMAIN TYPE  MODE        STATUS  REQUESTS  PENDING HWTYPE QDEPTH FUNCTIONS  DRIVER     
  --------------------------------------------------------------------------------------------
  01          CEX5C CCA-Coproc  online         1        0     11     08 ---D-----  cex4card   
  01.0001     CEX5C CCA-Coproc  online         1        0     11     08 ---D-----  cex4queue  

  
  [Regression Potential]

   * Changes are to an informational lszcrypt tool, output of which is
  now chnaged, but is not typically parsed in an automated fashion.
  (automation is usually done with lszdev/chzdev commands)

  [Other Info]

   * Original bug report:

  With the introduction of KVM crypto virtualization the driver bound to an AP queue device is no longer unique determined.
  This feature provides a deterministic hot plugging semantics of AP queues that may be bound to multiple drivers.
  In particular it enables to configure an AP queue (APQN) as being bound to a particular driver even if the associate HW gets intermittently lost and reconnected.

  s390-tools part.
  Backport from 2.7.0 to 2.6.0
  Git commit: for s390-tools 2.7.0

  https://github.com/ibm-s390-tools/s390-tools/commit/0a0b4c382693cded5652404e8fa2c0e483aa33df

  lszcrypt: support for alternate zcrypt device drivers

  It needs to be applied to 2.6.0 for Ubuntu 18.10, which will apply
  seamlessly

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