This bug was fixed in the package linux-snapdragon - 4.15.0-1071.78

---------------
linux-snapdragon (4.15.0-1071.78) bionic; urgency=medium

  * bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker (LP:
#1859793)

  * [ifc6640][db820c] enable support for UFS drive (LP: #1853556)
    - Revert "UBUNTU: [Config] disable PHY_QCOM_UFS"
    - Revert "UBUNTU: [Config] disable SCSI_UFSHCD"
    - Revert "dts: arm64/msm8996: Fix power domain for ufs"
    - Revert "arm64: dts: Add ufs dts nodes"
    - arm64: dts: qcom: msm8996: Add ufs related nodes
    - Revert "scsi: ufs: qcom: Expose the reset controller for PHY"
    - Revert "scsi: ufs: make UFS Tx lane1 clock optional for QCOM platforms"
    - Revert "scsi: ufs: ufshcd_dump_regs to use memcpy_fromio"
    - Revert "scsi: ufs: ufs-qcom: remove broken hci version quirk"
    - Revert "scsi/ufs: qcom: Remove ufs_qcom_phy_*() calls from host"
    - scsi/ufs: qcom: Remove ufs_qcom_phy_*() calls from host
    - scsi: ufs-qcom: Re-factor ufshcd_get_pwr_dev_param
    - scsi: ufs: Remove select of phy-qcom-ufs from ufs-qcom
    - scsi: ufs: qcom: Expose the reset controller for PHY
    - dt-bindings: ufs: Add #reset-cells for Qualcomm controllers
    - dt-bindings: phy-qcom-qmp: Add UFS PHY reset
    - dt-bindings: phy: qcom-ufs: Add resets property
    - arm64: dts: msm8996: Add UFS PHY reset controller
    - scsi: ufs: Introduce ufshcd_get_pwr_dev_param
    - phy: qcom-qmp: Drop useless msm8998_pciephy_cfg setting
    - phy: qcom-qmp: Raise qcom_qmp_phy_enable() polling delay
    - phy: qcom-qmp: Correct ready status, again
    - PCI: qcom: Use regulator bulk api for apq8064 supplies
    - PCI: qcom: Fix a bitwise vs logical NOT typo
    - PCI: qcom: Include gpio/consumer.h
    - PCI: qcom: Drop unnecessary root_bus_nr setting
    - PCI: Add Qualcomm vendor ID
    - PCI: qcom: Use default config space read function
    - PCI: qcom: Use clk bulk API for 2.4.0 controllers
    - phy: make phy-core explicitly non-modular
    - phy: core: Invoke pm_runtime_get_*/pm_runtime_put_* before invoking reset
      callback
    - SAUCE: phy: qcom-qmp: Increase PHY ready timeout
    - SAUCE: phy: qcom: qmp: Use power_on/off ops for PCIe
    - SAUCE: arm64: dts: msm8996: db820c: disable pcie1 bus

  [ Ubuntu: 4.15.0-75.85 ]

  * bionic/linux: 4.15.0-75.85 -proposed tracker (LP: #1859705)
  * use-after-free in i915_ppgtt_close (LP: #1859522) // CVE-2020-7053
    - SAUCE: drm/i915: Fix use-after-free when destroying GEM context
  * CVE-2019-14615
    - drm/i915/gen9: Clear residual context state on context switch
  * PAN is broken for execute-only user mappings on ARMv8 (LP: #1858815)
    - arm64: Revert support for execute-only user mappings
  * [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
    (LP: #1856608)
    - SAUCE: Revert "usb: handle warm-reset port requests on hub resume"
  * Miscellaneous Ubuntu changes
    - update dkms package versions

  [ Ubuntu: 4.15.0-74.84 ]

  * bionic/linux: 4.15.0-74.84 -proposed tracker (LP: #1856749)
  * [Hyper-V] KVP daemon fails to start on first boot of disco VM (LP: #1820063)
    - [Packaging] bind hv_kvp_daemon startup to hv_kvp device
  * Unrevert "arm64: Use firmware to detect CPUs that are not affected by
    Spectre-v2" (LP: #1854207)
    - arm64: Get rid of __smccc_workaround_1_hvc_*
    - arm64: Use firmware to detect CPUs that are not affected by Spectre-v2
  * Bionic kernel panic on Cavium ThunderX CN88XX (LP: #1853485)
    - SAUCE: irqchip/gic-v3-its: Add missing return value in
      its_irq_domain_activate()

 -- Manoj Iyer <manoj.i...@canonical.com>  Wed, 15 Jan 2020 15:14:22
-0600

** Changed in: linux-snapdragon (Ubuntu Bionic)
       Status: Confirmed => Fix Released

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

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

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

Title:
  bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  In Progress
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Bionic:
  Fix Released

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: '1860123'
  packages:
    main: linux-snapdragon
    meta: linux-meta-snapdragon
  phase: Promote to Updates
  phase-changed: Monday, 10. February 2020 13:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
    promote-to-security: Holding -- not ready for security (replication dwell)
    promote-to-updates: Ongoing -- packages not yet published
  trackers:
    bionic/linux-snapdragon/dragonboard-kernel: bug 1859791
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to