focal/linux-aws: 5.4.0-1109.118 -proposed tracker

[Roxana Nicolescu]

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 --
built:
  from: 4977cc8881cceaad
  route-entry: 1
delta:
  promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate]
  promote-to-security: []
  promote-to-updates: [lrm, lrs, main, meta, signed]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-9453
kernel-stable-master-bug: 2031128
packages:
  generate: linux-generate-aws
  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, 04. September 2023 21:03 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  bionic/linux-aws-5.4: bug 2030981
  focal/linux-aws-fips: bug 2030980
variant: debs
versions:
  lrm: 5.4.0-1109.118
  main: 5.4.0-1109.118
  meta: 5.4.0.1109.106
  signed: 5.4.0-1109.118
~~:
  clamps:
    new-review: 4977cc8881cceaad
    promote-to-proposed: 4977cc8881cceaad
    self: 5.4.0-1109.118
    sru-review: 4977cc8881cceaad

[Tim Gardner (timg-tpi)]

BT: 1109.117 passed boot testing. A no-change rebuild to fix the changelog won't affect that.

[Tim Gardner (timg-tpi)]

ADT: Updated hints. Tagging as passed.

[Tim Gardner (timg-tpi)]

RT: Updated hints. Tagging as passed.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-aws - 5.4.0-1109.118

---------------
linux-aws (5.4.0-1109.118) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1109.118 -proposed tracker (LP: #2030982)

  [ Ubuntu: 5.4.0-162.179 ]

  * focal/linux: 5.4.0-162.179 -proposed tracker (LP: #2031128)
  * libgnutls report "trap invalid opcode" when trying to install packages over
    https (LP: #2031093)
    - [Config]: disable CONFIG_GDS_FORCE_MITIGATION

  [ Ubuntu: 5.4.0-160.177 ]

  * focal/linux: 5.4.0-160.177 -proposed tracker (LP: #2031017)
  * Fix boot test warning for log_check "CPU: 0 PID: 0 at
    arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" (LP: #2031022)
    - x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to init_fpstate")

  [ Ubuntu: 5.4.0-158.175 ]

  * focal/linux: 5.4.0-158.175 -proposed tracker (LP: #2030466)
  * CVE-2022-40982
    - x86/mm: Initialize text poking earlier
    - x86/mm: fix poking_init() for Xen PV guests
    - x86/mm: Use mm_alloc() in poking_init()
    - mm: Move mm_cachep initialization to mm_init()
    - init: Provide arch_cpu_finalize_init()
    - x86/cpu: Switch to arch_cpu_finalize_init()
    - ARM: cpu: Switch to arch_cpu_finalize_init()
    - sparc/cpu: Switch to arch_cpu_finalize_init()
    - um/cpu: Switch to arch_cpu_finalize_init()
    - init: Remove check_bugs() leftovers
    - init: Invoke arch_cpu_finalize_init() earlier
    - init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
    - x86/fpu: Remove cpuinfo argument from init functions
    - x86/fpu: Mark init functions __init
    - x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
    - x86/xen: Fix secondary processors' FPU initialization
    - x86/speculation: Add Gather Data Sampling mitigation
    - x86/speculation: Add force option to GDS mitigation
    - x86/speculation: Add Kconfig option for GDS
    - KVM: Add GDS_NO support to KVM
    - Documentation/x86: Fix backwards on/off logic about YMM support
    - [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and
      CONFIG_GDS_FORCE_MITIGATION
  * CVE-2023-3609
    - net/sched: cls_u32: Fix reference counter leak leading to overflow
  * CVE-2023-20593
    - x86/cpu/amd: Move the errata checking functionality up
    - x86/cpu/amd: Add a Zenbleed fix
  * CVE-2023-3611
    - net/sched: sch_qfq: account for stab overhead in qfq_enqueue
  * stacked overlay file system mounts that have chroot() called against them
    appear to be getting locked (by the kernel most likely?) (LP: #2016398)
    - SAUCE: overlayfs: fix reference count mismatch
  * Focal update: v5.4.246 upstream stable release (LP: #2028981)
    - RDMA/efa: Fix unsupported page sizes in device
    - RDMA/bnxt_re: Enable SRIOV VF support on Broadcom's 57500 adapter series
    - RDMA/bnxt_re: Refactor queue pair creation code
    - RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx
    - iommu/rockchip: Fix unwind goto issue
    - iommu/amd: Don't block updates to GATag if guest mode is on
    - dmaengine: pl330: rename _start to prevent build error
    - net/mlx5: fw_tracer, Fix event handling
    - netrom: fix info-leak in nr_write_internal()
    - af_packet: Fix data-race...

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

All tasks have been completed and the bug is being closed