jammy/linux-gcp: 5.15.0-1005.8 -proposed tracker

Bug #1973899 reported by Stefan Bader
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Committed
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Boot-testing
Fix Released
Medium
Unassigned
Certification-testing
Invalid
Medium
Unassigned
New-review
Fix Released
Undecided
Unassigned
Prepare-package
Fix Released
Medium
Khaled El Mously
Prepare-package-lrg
Fix Released
Medium
Khaled El Mously
Prepare-package-lrm
Fix Released
Medium
Khaled El Mously
Prepare-package-lrs
Fix Released
Medium
Khaled El Mously
Prepare-package-meta
Fix Released
Medium
Khaled El Mously
Prepare-package-signed
Fix Released
Medium
Khaled El Mously
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
Fix Released
Medium
Andy Whitcroft
Promote-to-updates
Fix Released
Medium
Andy Whitcroft
Regression-testing
Invalid
Medium
Canonical Kernel Team
Security-signoff
Fix Released
Medium
Steve Beattie
Sru-review
Fix Released
Medium
Andy Whitcroft
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-gcp (Ubuntu)
Jammy
Fix Released
Medium
Unassigned

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
bugs-spammed: true
built:
  from: 4c6f3b27c8560ec5
  route-entry: 1
delta:
  promote-to-proposed: [lrm, meta, lrs, main, signed, lrg]
  promote-to-security: []
  promote-to-updates: [main, signed, lrm, lrs, meta]
issue: KSRU-2129
kernel-stable-master-bug: 1973924
packages:
  lrg: linux-restricted-generate-gcp
  lrm: linux-restricted-modules-gcp
  lrs: linux-restricted-signatures-gcp
  main: linux-gcp
  meta: linux-meta-gcp
  signed: linux-signed-gcp
phase: Complete
phase-changed: Tuesday, 24. May 2022 10:32 UTC
proposed-announcement-sent: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
trackers:
  focal/linux-gcp-5.15: bug 1973898
  kinetic/linux-gcp: bug 1973897
variant: debs
versions:
  lrm: 5.15.0-1005.8
  main: 5.15.0-1005.8
  meta: 5.15.0.1005.6
  signed: 5.15.0-1005.8
~~:
  clamps:
    new-review: 4c6f3b27c8560ec5
    promote-to-proposed: 4c6f3b27c8560ec5
    self: 5.15.0-1005.8
    sru-review: 4c6f3b27c8560ec5

CVE References

Stefan Bader (smb)
tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2022.04.18-9
description: updated
tags: added: kernel-sru-derivative-of-1973924
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-gcp (Ubuntu Jammy):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
tags: added: kernel-jira-issue-ksru-2129
description: updated
description: updated
description: updated
summary: - jammy/linux-gcp: <version to be filled> -proposed tracker
+ jammy/linux-gcp: 5.15.0-1005.8 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Andy Whitcroft (apw)
tags: added: kernel-signing-bot
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (7.5 KiB)

This bug was fixed in the package linux-gcp - 5.15.0-1005.8

---------------
linux-gcp (5.15.0-1005.8) jammy; urgency=medium

  * jammy/linux-gcp: 5.15.0-1005.8 -proposed tracker (LP: #1973899)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync getabis
    - [Packaging] update Ubuntu.md

  [ Ubuntu: 5.15.0-33.34 ]

  * jammy/linux: 5.15.0-33.34 -proposed tracker (LP: #1973924)
  * CVE-2022-29581
    - net/sched: cls_u32: fix netns refcount changes in u32_change()
  * ext4: limit length to bitmap_maxbytes (LP: #1972281)
    - ext4: limit length to bitmap_maxbytes - blocksize in punch_hole
  * Unprivileged users may use PTRACE_SEIZE to set PTRACE_O_SUSPEND_SECCOMP
    option (LP: #1972740)
    - ptrace: Check PTRACE_O_SUSPEND_SECCOMP permission on PTRACE_SEIZE

  [ Ubuntu: 5.15.0-30.31 ]

  * jammy/linux: 5.15.0-30.31 -proposed tracker (LP: #1971685)
  * Packaging resync (LP: #1786013)
    - [Packaging] update variants
    - debian/dkms-versions -- update from kernel-versions (main/2022.04.18)
  * Intel: enable x86 AMX (LP: #1967750)
    - x86/extable: Tidy up redundant handler functions
    - x86/extable: Get rid of redundant macros
    - x86/mce: Deduplicate exception handling
    - x86/mce: Get rid of stray semicolons
    - x86/extable: Rework the exception table mechanics
    - x86/extable: Provide EX_TYPE_DEFAULT_MCE_SAFE and EX_TYPE_FAULT_MCE_SAFE
    - x86/copy_mc: Use EX_TYPE_DEFAULT_MCE_SAFE for exception fixups
    - x86/fpu: Use EX_TYPE_FAULT_MCE_SAFE for exception fixups
    - x86/extable: Remove EX_TYPE_FAULT from MCE safe fixups
    - x86/fpu/signal: Clarify exception handling in restore_fpregs_from_user()
    - x86/fpu/signal: Move header zeroing out of xsave_to_user_sigframe()
    - x86/fpu/signal: Move xstate clearing out of copy_fpregs_to_sigframe()
    - x86/fpu/signal: Change return type of copy_fpstate_to_sigframe() to boolean
    - x86/fpu/signal: Change return type of copy_fpregs_to_sigframe() helpers to
      boolean
    - x86/signal: Change return type of restore_sigcontext() to boolean
    - x86/fpu/signal: Change return type of fpu__restore_sig() to boolean
    - x86/fpu/signal: Change return type of __fpu_restore_sig() to boolean
    - x86/fpu/signal: Change return code of check_xstate_in_sigframe() to boolean
    - x86/fpu/signal: Change return code of restore_fpregs_from_user() to boolean
    - x86/fpu/signal: Fix missed conversion to correct boolean retval in
      save_xstate_epilog()
    - x86/fpu: Remove pointless argument from switch_fpu_finish()
    - x86/fpu: Update stale comments
    - x86/pkru: Remove useless include
    - x86/fpu: Restrict xsaves()/xrstors() to independent states
    - x86/fpu: Cleanup the on_boot_cpu clutter
    - x86/fpu: Remove pointless memset in fpu_clone()
    - x86/process: Clone FPU in copy_thread()
    - x86/fpu: Do not inherit FPU context for kernel and IO worker threads
    - x86/fpu: Cleanup xstate xcomp_bv initialization
    - x86/fpu/xstate: Provide and use for_each_xfeature()
    - x86/fpu/xstate: Mark all init only functions __init
    - x86/fpu: Move KVMs FPU swapping to FPU core
    - x86/fpu: Replace KVMs home brewed FPU copy from user
    - x86/fpu: Rework c...

Read more...

Changed in linux-gcp (Ubuntu Jammy):
status: New → Fix Released
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Workflow done!

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

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
tags: removed: kernel-release-tracking-bug-live
Andy Whitcroft (apw)
Changed in kernel-sru-workflow:
status: Fix Released → Fix Committed
description: updated
Andy Whitcroft (apw)
tags: added: kernel-release-tracking-bug-live
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers