group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1801686@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux - 4.15.0-42.45

---------------
linux (4.15.0-42.45) bionic; urgency=medium

  * linux: 4.15.0-42.45 -proposed tracker (LP: #1803592)

  * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405)
    - KVM: s390: reset crypto attributes for all vcpus
    - KVM: s390: vsie: simulate VCPU SIE entry/exit
    - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART
    - KVM: s390: refactor crypto initialization
    - s390: vfio-ap: base implementation of VFIO AP device driver
    - s390: vfio-ap: register matrix device with VFIO mdev framework
    - s390: vfio-ap: sysfs interfaces to configure adapters
    - s390: vfio-ap: sysfs interfaces to configure domains
    - s390: vfio-ap: sysfs interfaces to configure control domains
    - s390: vfio-ap: sysfs interface to view matrix mdev matrix
    - KVM: s390: interface to clear CRYCB masks
    - s390: vfio-ap: implement mediated device open callback
    - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl
    - s390: vfio-ap: zeroize the AP queues
    - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl
    - KVM: s390: Clear Crypto Control Block when using vSIE
    - KVM: s390: vsie: Do the CRYCB validation first
    - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear
    - KVM: s390: vsie: Allow CRYCB FORMAT-2
    - KVM: s390: vsie: allow CRYCB FORMAT-1
    - KVM: s390: vsie: allow CRYCB FORMAT-0
    - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1
    - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2
    - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2
    - KVM: s390: device attrs to enable/disable AP interpretation
    - KVM: s390: CPU model support for AP virtualization
    - s390: doc: detailed specifications for AP virtualization
    - KVM: s390: fix locking for crypto setting error path
    - KVM: s390: Tracing APCB changes
    - s390: vfio-ap: setup APCB mask using KVM dedicated function
    - s390/zcrypt: Add ZAPQ inline function.
    - s390/zcrypt: Review inline assembler constraints.
    - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.
    - s390/zcrypt: fix ap_instructions_available() returncodes
    - s390/zcrypt: remove VLA usage from the AP bus
    - s390/zcrypt: Remove deprecated ioctls.
    - s390/zcrypt: Remove deprecated zcrypt proc interface.
    - s390/zcrypt: Support up to 256 crypto adapters.
    - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module.

  * Bypass of mount visibility through userns + mount propagation (LP: #1789161)
    - mount: Retest MNT_LOCKED in do_umount
    - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts

  *  CVE-2018-18955: nested user namespaces with more than five extents
    incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955
    - userns: also map extents in the reverse map to kernel IDs

  * kdump fail due to an IRQ storm (LP: #1797990)
    - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code
    - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot
    - SAUCE: x86/quirks: Scan all busses for early PCI quirks

 -- Thadeu Lima de Souza Cascardo <cascardo@xxxxxxxxxxxxx>  Thu, 15 Nov
2018 17:01:46 -0200

** Changed in: linux (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18955

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1801686

Title:
  [Ubuntu] qdio: reset old sbal_state flags

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==

  Description: qdio: reset old sbal_state flags

  Symptom:
     af_iucv socket using HiperSockets may stall.
  Problem:
     When allocating a new AOB fails, handle_outbound() is
  still capable of transmitting the selected buffer
  (just without async completion).
  But if a previous transfer on this queue slot used
  async completion, its sbal_state flags field is still set
  to QDIO_OUTBUF_STATE_FLAG_PENDING.
  So when the upper layer driver sees this stale flag, it
  expects an async completion that never happens.
  Solution:
     Unconditionally clear the buffer's flags field.

  == Fix ==

  64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
  sbal_state flags")

  == Regression Potential ==

  Low, because:
  - s390x only
  - further limited to qeth driver (OSA Express networking)
  - changes are limited to two files and 6 lines
     - arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
     - drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
  - error was identified at IBM/customer, fix was created there and tested upfront
  - (changes are upstream in 4.20 (according to bug description,
     but in 4.19 according to 'git tag'),
     hence will make it automatically into 'disco')

  == Test Case ==

  Test case / reproduction:
  Error inject and then simulate out-of-memory situation.

  __________

  Description:  qdio: reset old sbal_state flags

  Symptom:      af_iucv socket using HiperSockets may stall.

  Problem:      When allocating a new AOB fails, handle_outbound() is
                still capable of transmitting the selected buffer
                (just without async completion).
                But if a previous transfer on this queue slot used
                async completion, its sbal_state flags field is still set
                to QDIO_OUTBUF_STATE_FLAG_PENDING.
                So when the upper layer driver sees this stale flag, it
                expects an async completion that never happens.

  Solution:     Unconditionally clear the buffer's flags field.

  Reproduction: Error inject, simulating out-of-memory.

  kernel 4.20
  Upstream-ID:  64e03ff72623b8c2ea89ca3cb660094e019ed4ae

  Canonical , please provide this fix for all Releases in Service....
  Ubuntu 18.10, 18.04 and 16.04

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