impish/linux-aws: 5.13.0-1014.15 -proposed tracker

[Tim Gardner]

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
bugs-spammed: true
built:
  route-entry: 1
delta:
  promote-to-proposed:
  - lrm
  - signed
  - lrs
  - main
  - meta
  - lrg
  promote-to-security: []
  promote-to-updates:
  - main
  - lrm
  - lrs
  - meta
  - signed
  sru-review:
  - lrg
  - lrs
  - signed
  - lrm
  - main
  - meta
issue: KSRU-1095
kernel-stable-master-bug: 1960055
packages:
  lrg: linux-restricted-generate-aws
  lrm: linux-restricted-modules-aws
  lrs: linux-restricted-signatures-aws
  main: linux-aws
  meta: linux-meta-aws
  signed: linux-signed-aws
phase: Complete
phase-changed: Monday, 21. February 2022 21:39 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  focal/linux-aws-5.13: bug 1961082
variant: debs
versions:
  lrm: 5.13.0-1014.15
  main: 5.13.0-1014.15
  meta: 5.13.0.1014.15
  signed: 5.13.0-1014.15
versions-clamp:
  self: 5.13.0-1014.15

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

The following packages ended up in the wrong component in the Proposed pocket:

linux-signed-aws 5.13.0-1014.15 - is in universe instead of main
linux-image-5.13.0-1014-aws 5.13.0-1014.15 - is in universe instead of main
linux-image-5.13.0-1014-aws 5.13.0-1014.15 - is in universe instead of main
linux-image-5.13.0-1014-aws-dbgsym 5.13.0-1014.15 - is in universe instead of main
linux-image-5.13.0-1014-aws-dbgsym 5.13.0-1014.15 - is in universe instead of main

Once this is fixed, set the promote-to-proposed to Fix Released again

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-aws - 5.13.0-1014.15

---------------
linux-aws (5.13.0-1014.15) impish; urgency=medium

  * impish/linux-aws: 5.13.0-1014.15 -proposed tracker (LP: #1960525)

  * linux-aws: Make a signed kernel (LP: #1951011)
    - [Packaging] aws: Make a signed kernel

linux-aws (5.13.0-1013.14) impish; urgency=medium

  * impish/linux-aws: 5.13.0-1013.14 -proposed tracker (LP: #1960042)

  * tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
    - [Packaging] aws: Include tcm_loop.ko

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
    (LP: #1960034)
    - Revert "block: avoid to quiesce queue in elevator_init_mq"
    - Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
      disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
    - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
    - drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
    - ACPI: Get acpi_device's parent from the parent field
    - USB: serial: option: add Telit LE910S1 0x9200 composition
    - USB: serial: option: add Fibocom FM101-GL variants
    - usb: dwc2: gadget: Fix ISOC flow for elapsed frames
    - usb: dwc2: hcd_queue: Fix use of floating point literal
    - usb: dwc3: gadget: Ignore NoStream after End Transfer
    - usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
    - usb: dwc3: gadget: Fix null pointer exception
    - net: nexthop: fix null pointer dereference when IPv6 is not enabled
    - usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe
    - usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
    - usb: hub: Fix usb enumeration issue due to address0 race
    - usb: hub: Fix locking issues with address0_mutex
    - binder: fix test regression due to sender_euid change
    - ALSA: ctxfi: Fix out-of-range access
    - ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
    - ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
    - media: cec: copy sequence field for the reply
    - Revert "parisc: Fix backtrace to always include init funtion names"
    - HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
    - staging/fbtft: Fix backlight
    - staging: greybus: Add missing rwsem around snd_ctl_remove() calls
    - staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
    - fuse: release pipe buf after last use
    - xen: don't continue xenstore initialization in case of errors
    - xen: detect uninitialized xenbus in xenbus_init
    - KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
    - tracing/uprobe: Fix uprobe_perf_open probes iteration
    - tracing: Fix pid filtering when triggers are attached
    - mmc: sdhci-esdhc-imx: disable CMDQ support
    - mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
   ...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being set to Fix Released