mantic/linux-starfive: 6.5.0-1001.2 -proposed tracker

[Paolo Pisati]

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: cab20de2c7974474
  route-entry: 1
delta:
  promote-to-proposed: [main, meta]
flag:
  boot-testing-requested: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
kernel-stable-master-bug: 2037611
packages:
  main: linux-starfive
  meta: linux-meta-starfive
phase: Testing
phase-changed: Saturday, 07. October 2023 20:45 UTC
reason:
  kernel-signoff: Stalled -s waiting for signoff
  regression-testing: Stalled -s testing FAILED
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 6.5.0-1001.2
  meta: 6.5.0.1001.3
~~:
  announce:
    swm-transition-crankable: 2023-10-03 19:30:37.690963
  clamps:
    new-review: cab20de2c7974474
    promote-to-proposed: cab20de2c7974474
    self: 6.5.0-1001.2
    sru-review: cab20de2c7974474

[Andy Whitcroft (apw)]

Producing linux-source-6.5.0 which is not appropriate for a derivative.

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

linux-image major version change detected, upgrade testing required; kernel-signoff required.

[Andy Whitcroft (apw)]

Producing linux-source-6.5.0 which is inappropriate for a deriviative.

[Andy Whitcroft (apw)]

linux-source ...

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

linux-image major version change detected, upgrade testing required; kernel-signoff required.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-starfive - 6.5.0-1002.3

---------------
linux-starfive (6.5.0-1002.3) mantic; urgency=medium

  * mantic/linux-starfive: 6.5.0-1002.3 -proposed tracker (LP: #2038697)

  [ Ubuntu: 6.5.0-9.9 ]

  * mantic/linux: 6.5.0-9.9 -proposed tracker (LP: #2038687)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - re-apply apparmor 4.0.0
  * Disable restricting unprivileged change_profile by default, due to LXD
    latest/stable not yet compatible with this new apparmor feature
    (LP: #2038567)
    - SAUCE: apparmor: Make apparmor_restrict_unprivileged_unconfined opt-in

  [ Ubuntu: 6.5.0-8.8 ]

  * mantic/linux: 6.5.0-8.8 -proposed tracker (LP: #2038577)
  * update apparmor and LSM stacking patch set (LP: #2028253)
    - SAUCE: apparmor3.2.0 [02/60]: rename SK_CTX() to aa_sock and make it an
      inline fn
    - SAUCE: apparmor3.2.0 [05/60]: Add sysctls for additional controls of unpriv
      userns restrictions
    - SAUCE: apparmor3.2.0 [08/60]: Stacking v38: LSM: Identify modules by more
      than name
    - SAUCE: apparmor3.2.0 [09/60]: Stacking v38: LSM: Add an LSM identifier for
      external use
    - SAUCE: apparmor3.2.0 [10/60]: Stacking v38: LSM: Identify the process
      attributes for each module
    - SAUCE: apparmor3.2.0 [11/60]: Stacking v38: LSM: Maintain a table of LSM
      attribute data
    - SAUCE: apparmor3.2.0 [12/60]: Stacking v38: proc: Use lsmids instead of lsm
      names for attrs
    - SAUCE: apparmor3.2.0 [13/60]: Stacking v38: integrity: disassociate
      ima_filter_rule from security_audit_rule
    - SAUCE: apparmor3.2.0 [14/60]: Stacking v38: LSM: Infrastructure management
      of the sock security
    - SAUCE: apparmor3.2.0 [15/60]: Stacking v38: LSM: Add the lsmblob data
      structure.
    - SAUCE: apparmor3.2.0 [16/60]: Stacking v38: LSM: provide lsm name and id
      slot mappings
    - SAUCE: apparmor3.2.0 [17/60]: Stacking v38: IMA: avoid label collisions with
      stacked LSMs
    - SAUCE: apparmor3.2.0 [18/60]: Stacking v38: LSM: Use lsmblob in
      security_audit_rule_match
    - SAUCE: apparmor3.2.0 [19/60]: Stacking v38: LSM: Use lsmblob in
      security_kernel_act_as
    - SAUCE: apparmor3.2.0 [20/60]: Stacking v38: LSM: Use lsmblob in
      security_secctx_to_secid
    - SAUCE: apparmor3.2.0 [21/60]: Stacking v38: LSM: Use lsmblob in
      security_secid_to_secctx
    - SAUCE: apparmor3.2.0 [22/60]: Stacking v38: LSM: Use lsmblob in
      security_ipc_getsecid
    - SAUCE: apparmor3.2.0 [23/60]: Stacking v38: LSM: Use lsmblob in
      security_current_getsecid
    - SAUCE: apparmor3.2.0 [24/60]: Stacking v38: LSM: Use lsmblob in
      security_inode_getsecid
    - SAUCE: apparmor3.2.0 [25/60]: Stacking v38: LSM: Use lsmblob in
      security_cred_getsecid
    - SAUCE: apparmor3.2.0 [26/60]: Stacking v38: LSM: Specify which LSM to
      display
    - SAUCE: apparmor3.2.0 [28/60]: Stacking v38: LSM: Ensure the correct LSM
      context releaser
    - SAUCE: apparmor3.2.0 [29/60]: Stacking v38: LSM: Use lsmcontext in
      security_secid_to_secctx
    - SAUCE: apparmor3.2.0 [30/60]: Stacking v38: LSM: Use lsmcontext in
      security_inode_...