noble/linux-riscv: 6.8.0-28.28.1 -proposed tracker

Bug #2061974 reported by Emil Renner Berthing
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Abi-testing
Fix Released
Medium
Unassigned
Automated-testing
Invalid
Medium
Unassigned
Boot-testing
Fix Released
Medium
Unassigned
New-review
Fix Released
Medium
Andy Whitcroft
Prepare-package
Fix Released
Medium
Emil Renner Berthing
Prepare-package-meta
Fix Released
Medium
Emil Renner Berthing
Promote-to-proposed
Fix Released
Medium
Canonical Kernel Team
Promote-to-release
Fix Released
Medium
Ubuntu Package Archive Administrators
Regression-testing
Fix Released
Medium
Canonical Kernel Team
Sru-review
Fix Released
Medium
Andy Whitcroft
canonical-signing-jobs
Task00
Fix Released
Medium
Andy Whitcroft
linux-riscv (Ubuntu)
Noble
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 --
built:
  from: 60d2a921dec8853a
  route-entry: 2
comments:
  abi-testing: 1
delta:
  promote-to-proposed: [main, meta]
  promote-to-release: [main, meta]
flag:
  boot-testing-requested: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
packages:
  main: linux-riscv
  meta: linux-meta-riscv
phase: Complete
phase-changed: Friday, 19. April 2024 20:42 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 6.8.0-28.28.1
  meta: 6.8.0-28.28.1
~~:
  announce:
    swm-transition-crankable: 2024-04-17 08:27:07.452166
  clamps:
    new-review: 60d2a921dec8853a
    promote-to-proposed: 60d2a921dec8853a
    self: 6.8.0-28.28.1
    sru-review: 60d2a921dec8853a
  tracker:
    last-message: '2024-04-19 21:46:02.027916+00:00'

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-d2024.04.04-1
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-riscv (Ubuntu Noble):
importance: Undecided → Medium
tags: added: kernel-block-derivatives
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
summary: - noble/linux-riscv: <version to be filled> -proposed tracker
+ noble/linux-riscv: 6.8.0-28.28.1 -proposed tracker
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Ancillary Bot (ubuntu-kernel-ancillary-bot) wrote : ABI testing

riscv64/generic canonical-certs.pem unchanged
riscv64/generic canonical-revoked-certs.pem unchanged
riscv64/generic fwinfo unchanged
riscv64/generic modules unchanged

description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
tags: added: boot-testing-passed
description: updated
description: updated
description: updated
description: updated
description: updated
tags: added: regression-testing-passed
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (11.9 KiB)

This bug was fixed in the package linux-riscv - 6.8.0-28.28.1

---------------
linux-riscv (6.8.0-28.28.1) noble; urgency=medium

  * noble/linux-riscv: 6.8.0-28.28.1 -proposed tracker (LP: #2061974)

  * Packaging resync (LP: #1786013)
    - [Packaging] drop getabis data
    - [Packaging] debian.riscv/dkms-versions -- update from kernel-versions
      (main/d2024.04.04)

  * Enable Milk-V Mars board (LP: #2061897)
    - SAUCE: riscv: dts: starfive: add 'cpus' label to jh7110 and jh7100 soc dtsi
    - SAUCE: dt-bindings: riscv: starfive: add Milkv Mars board
    - SAUCE: riscv: dts: starfive: visionfive 2: update sound and codec dt node
      name
    - SAUCE: riscv: dts: starfive: visionfive 2: use cpus label for timebase freq
    - SAUCE: riscv: dts: starfive: introduce a common board dtsi for jh7110 based
      boards
    - SAUCE: riscv: dts: starfive: add Milkv Mars board device tree

  * Enable StarFive VisionFive 2 board (LP: #2013232)
    - SAUCE: riscv: dts: starfive: visionfive 2: Remove non-existing TDM hardware
    - SAUCE: riscv: dts: starfive: visionfive 2: Remove non-existing I2S hardware

  [ Ubuntu: 6.8.0-28.28 ]

  * noble/linux: 6.8.0-28.28 -proposed tracker (LP: #2061867)
  * linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor
    profiles/features (LP: #2061851)
    - SAUCE: apparmor4.0.0 [92/90]: fix address mapping for recvfrom

  [ Ubuntu: 6.8.0-25.25 ]

  * noble/linux: 6.8.0-25.25 -proposed tracker (LP: #2061083)
  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/d2024.04.04)
  * Apply mitigations for the native BHI hardware vulnerabilty (LP: #2060909)
    - x86/cpufeatures: Add new word for scattered features
    - x86/bugs: Change commas to semicolons in 'spectre_v2' sysfs file
    - x86/syscall: Don't force use of indirect calls for system calls
    - x86/bhi: Add support for clearing branch history at syscall entry
    - x86/bhi: Define SPEC_CTRL_BHI_DIS_S
    - x86/bhi: Enumerate Branch History Injection (BHI) bug
    - x86/bhi: Add BHI mitigation knob
    - x86/bhi: Mitigate KVM by default
    - KVM: x86: Add BHI_NO
    - x86: set SPECTRE_BHI_ON as default
    - [Config] enable spectre_bhi=auto by default
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor4.0.0 [01/90]: LSM stacking v39: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor4.0.0 [02/90]: LSM stacking v39: SM: Infrastructure
      management of the sock security
    - SAUCE: apparmor4.0.0 [03/90]: LSM stacking v39: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor4.0.0 [04/90]: LSM stacking v39: IMA: avoid label collisions
      with stacked LSMs
    - SAUCE: apparmor4.0.0 [05/90]: LSM stacking v39: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor4.0.0 [06/90]: LSM stacking v39: LSM: Add lsmblob_to_secctx
      hook
    - SAUCE: apparmor4.0.0 [07/90]: LSM stacking v39: Audit: maintain an lsmblob
      in audit_context
    - SAUCE: apparmor4.0.0 [08/90]: LSM stacking v39: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor4....

Changed in linux-riscv (Ubuntu Noble):
status: New → Fix Released
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 closed

Changed in kernel-sru-workflow:
status: In Progress → Fix Committed
description: updated
Changed in kernel-sru-workflow:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.