AppArmor patch for mq-posix interface is missing in jammy

Bug #2045384 reported by Masahiro Nakagawa
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned
Jammy
Fix Released
Medium
Unassigned
linux-hwe (Ubuntu)
New
Undecided
Unassigned
Focal
New
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
livecd-rootfs (Ubuntu)
New
Undecided
Unassigned
Focal
New
Undecided
Unassigned
Jammy
New
Undecided
Unassigned

Bug Description

[ Impact ]

mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected.

Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error.

The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel.

Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel.

[ Test Plan ]

 * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel.
 * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client

[ Where problems could occur ]

 * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues.

[ Other Info ]

 * This is a time-sensitive issue for a paying customer

Revision history for this message
Masahiro Nakagawa (masahiro20200511) wrote :
Isaac True (itrue)
description: updated
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Please use 22-hwe/stable if you can, please let us know if that's acceptable.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Masahiro Nakagawa (masahiro20200511) wrote :

No they cannot use 22-hwe/stable.

I talked to this customer and they cannot accept kernel version change. (ABI interface and other minor changes maybe introduced by 6.2 kernel and they cannot take this risk)

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

If/when this lands in jammy 5.15 it will affect snapd-preseed status in livecd-rootfs which will need to have appropriate adjustment as well, at the same time.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Stefan Bader (smb)
Changed in linux (Ubuntu Jammy):
importance: Undecided → Medium
status: New → Triaged
Changed in linux (Ubuntu Jammy):
status: Triaged → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.15.0-94.104 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux
Revision history for this message
Isaac True (itrue) wrote :

Confirmed fixed in linux/5.15.0-94.104 using the itrue-mqtest-provider and itrue-mqtest-client snaps.

Test procedure:

sudo snap install itrue-mqtest-provider itrue-mqtest-client
sudo snap connect itrue-mqtest-client:itrue-mqtest-all-perms itrue-mqtest-provider:itrue-mqtest-all-perms
sudo snap connect itrue-mqtest-client:itrue-mqtest-default itrue-mqtest-provider:itrue-mqtest-default
sudo snap connect itrue-mqtest-client:itrue-mqtest-ro itrue-mqtest-provider:itrue-mqtest-ro
sudo snap connect itrue-mqtest-client:itrue-mqtest-rw itrue-mqtest-provider:itrue-mqtest-rw

Before upgrading (on kernel 5.15.0-1048-kvm):

ubuntu@concise-pangolin:~$ sudo itrue-mqtest-provider
MQ "/test-default" failed: File exists
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-client.all
MQ "/test-all-perms" failed: Operation not permitted
Test failed

After upgrading (5.15.0-94-generic):

(in first terminal)
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-provider
MQ "/test-default" created
MQ "/test-ro" created
MQ "/test-rw" created
MQ "/test-all-perms" created
MQ "/test-default": 0xDEADBEEF
MQ "/test-all-perms": 0xDEADBEEF

(in second terminal)
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-client.default
Test succeeded
ubuntu@concise-pangolin:~$ sudo itrue-mqtest-client.all
Test succeeded

Revision history for this message
Georgia Garcia (georgiag) wrote :

Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue tests from the AppArmor test suite and they all passed as expected.

georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ uname -a
Linux sec-jammy-amd64 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py
.....
----------------------------------------------------------------------
Ran 62 tests in 1252.754s

OK (skipped=2)

georgia@sec-jammy-amd64:~$ apt source apparmor
georgia@sec-jammy-amd64:~$ cd apparmor-3.0.4/tests/regression/apparmor/
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ USE_SYSTEM=1 make
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ sudo ./posix_mq.sh
BAD PASSWORD: The password fails the dictionary check - it is based on a dictionary word
xpass: POSIX MQUEUE (confined root - mqueue label 1)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined root - mqueue label 2)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll)

[1] https://launchpad.net/qa-regression-testing

tags: added: verification-done-jammy-linux
removed: verification-needed-jammy-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-intel-iotg/5.15.0-1047.53 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-done-jammy-linux-intel-iotg'. If the problem still exists, change the tag 'verification-needed-jammy-linux-intel-iotg' to 'verification-failed-jammy-linux-intel-iotg'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-intel-iotg-v2 verification-needed-jammy-linux-intel-iotg
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-ibm-gt-fips/5.15.0-1052.55+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-ibm-gt-fips' to 'verification-done-jammy-linux-ibm-gt-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-gt-fips' to 'verification-failed-jammy-linux-ibm-gt-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-ibm-gt-fips-v2 verification-needed-jammy-linux-ibm-gt-fips
Revision history for this message
Georgia Garcia (georgiag) wrote :

Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue tests from the AppArmor test suite and they all passed as expected.

georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ uname -a
Linux sec-jammy-amd64 5.15.0-1048-intel-iotg #54-Ubuntu SMP Thu Jan 18 18:39:09 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py
.....
----------------------------------------------------------------------
Ran 62 tests in 1246.031s

OK (skipped=2)

georgia@sec-jammy-amd64:/tmp$ apt source apparmor
georgia@sec-jammy-amd64:/tmp$ cd apparmor-3.0.4/tests/regression/apparmor/
georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ USE_SYSTEM=1 make
georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ sudo ./posix_mq.sh
[sudo] password for georgia:
BAD PASSWORD: The password fails the dictionary check - it is based on a dictionary word
xpass: POSIX MQUEUE (confined root - mqueue label 1)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined root - mqueue label 2)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll)

[1] https://launchpad.net/qa-regression-testing

tags: added: verification-done-jammy-linux-intel-iotg
removed: verification-needed-jammy-linux-intel-iotg
Revision history for this message
Georgia Garcia (georgiag) wrote :

Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue tests from the AppArmor test suite and they all passed as expected.

georgia@sec-jammy-amd64:~$ uname -a
Linux sec-jammy-amd64 5.15.0-1052-ibm-gt-fips #55+fips1-Ubuntu SMP Fri Jan 19 23:25:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py
.....
----------------------------------------------------------------------
Ran 62 tests in 1120.042s

OK (skipped=2)

georgia@sec-jammy-amd64:/tmp$ apt source apparmor
georgia@sec-jammy-amd64:/tmp$ cd apparmor-3.0.4/tests/regression/apparmor/
georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ USE_SYSTEM=1 make
georgia@sec-jammy-amd64:/tmp/apparmor-3.0.4/tests/regression/apparmor$ sudo ./posix_mq.sh
[sudo] password for georgia:
BAD PASSWORD: The password fails the dictionary check - it is based on a dictionary word
xpass: POSIX MQUEUE (confined root - mqueue label 1)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined root - mqueue label 2)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll)

[1] https://launchpad.net/qa-regression-testing

tags: added: verification-done-jammy-linux-ibm-gt-fips
removed: verification-needed-jammy-linux-ibm-gt-fips
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (63.2 KiB)

This bug was fixed in the package linux - 5.15.0-94.104

---------------
linux (5.15.0-94.104) jammy; urgency=medium

  * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777)

  * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
    (LP: #2028158)
    - device-dax: Fix duplicate 'hmem' device registration

  * Add ODM driver f81604 usb-can (LP: #2045387)
    - can: usb: f81604: add Fintek F81604 support
    - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604

  * Add ODM driver gpio-m058ssan (LP: #2045386)
    - SAUCE: ODM: gpio: add M058SSAN gpio driver
    - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN

  * Add ODM driver rtc-pcf85263 (LP: #2045385)
    - SAUCE: ODM: rtc: add PCF85263 RTC driver
    - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263

  * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384)
    - SAUCE: (no-up) apparmor: reserve mediation classes
    - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues

  * Packaging resync (LP: #1786013)
    - [Packaging] update annotations scripts

linux (5.15.0-93.103) jammy; urgency=medium

  * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync update-dkms-versions helper
    - [Packaging] remove helper scripts
    - [Packaging] update annotations scripts
    - debian/dkms-versions -- update from kernel-versions (main/2024.01.08)

  * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382)
    - Revert "PCI: acpiphp: Reassign resources on bridge if necessary"

  * CVE-2023-6622
    - netfilter: nf_tables: bail out on mismatching dynset and set expressions

  * CVE-2024-0193
    - netfilter: nf_tables: skip set commit for deleted/destroyed sets

  * CVE-2023-6040
    - netfilter: nf_tables: Reject tables of unsupported family

  * Patches needed for AmpereOne (arm64) (LP: #2044192)
    - clocksource/arm_arch_timer: Add build-time guards for unhandled register
      accesses
    - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors
    - clocksource/drivers/arm_arch_timer: Extend write side of timer register
      accessors to u64
    - clocksource/drivers/arm_arch_timer: Move system register timer programming
      over to CVAL
    - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function
      names
    - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback
      ordering issue
    - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL
    - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code
    - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations
    - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL programming
      interface
    - clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL programming
    - clocksource/drivers/arm_arch_timer: Fix masking for high freq counters
    - clocksource/drivers/arch_arm_timer: Move workaround synchronisation around

  * Add quirk to disable i915 fastboot on B&R PC (LP: #2047630)
    - SAUCE: i915...

Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-bluefield/5.15.0-1035.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-bluefield-v2 verification-needed-jammy-linux-bluefield
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-raspi/5.15.0-1046.49 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-done-jammy-linux-raspi'. If the problem still exists, change the tag 'verification-needed-jammy-linux-raspi' to 'verification-failed-jammy-linux-raspi'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-raspi-v2 verification-needed-jammy-linux-raspi
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/5.15.0-1056.64 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy-linux-azure'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure
Revision history for this message
Georgia Garcia (georgiag) wrote :

Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue tests from the AppArmor test suite and they all passed as expected.

georgia@sec-jammy-amd64:~$ uname -a
Linux sec-jammy-amd64 5.15.0-1056-azure #64-Ubuntu SMP Tue Feb 6 19:23:34 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

georgia@sec-jammy-amd64:~/qrt-test-apparmor$ sudo ./test-apparmor.py
.....
----------------------------------------------------------------------
Ran 62 tests in 1061.185s

OK (skipped=2)

georgia@sec-jammy-amd64:~$ apt source apparmor
georgia@sec-jammy-amd64:~$ cd apparmor-3.0.4/tests/regression/apparmor/
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ USE_SYSTEM=1 make
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ sudo ./posix_mq.sh
BAD PASSWORD: The password fails the dictionary check - it is based on a dictionary word
xpass: POSIX MQUEUE (confined root - mqueue label 1)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined root - mqueue label 2)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 1)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : mq_notify)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : select)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : poll)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 1 : epoll)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 2)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : mq_notify)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : select)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : poll)
xpass: POSIX MQUEUE (confined 1002 - mqueue label 2 : epoll)

[1] https://launchpad.net/qa-regression-testing

tags: added: verification-done-jammy-linux-azure
removed: verification-needed-jammy-linux-azure
Revision history for this message
Georgia Garcia (georgiag) wrote :

I could confirm that the patches are present in linux-bluefield and linux-raspi: 6e7ff802c7b10 and b4ebbcfebd4d3

tags: added: verification-done-jammy-linux-bluefield verification-done-jammy-linux-raspi verification-needed-jammy-linux-azure
removed: verification-done-jammy-linux-azure verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-raspi
tags: added: verification-done-jammy-linux-azure
removed: verification-needed-jammy-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra/5.15.0-1022.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-xilinx-zynqmp/5.15.0-1027.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp' to 'verification-failed-jammy-linux-xilinx-zynqmp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Georgia Garcia (georgiag) wrote :

I can confirm that the mqueue patches are present in linux-xilinx-zynqmp: commits 6e7ff802c7b10 and b4ebbcfebd4d3

tags: added: verification-done-jammy-linux-xilinx-zynqmp
removed: verification-needed-jammy-linux-xilinx-zynqmp
Revision history for this message
Georgia Garcia (georgiag) wrote :

The mqueue patches are present in linux-nvidia-tegra: commits 6e7ff802c7b10 and b4ebbcfebd4d3

tags: added: verification-done-jammy-linux-nvidia-tegra
removed: verification-needed-jammy-linux-nvidia-tegra
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-fips/5.15.0-1058.66+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-done-jammy-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-fips' to 'verification-failed-jammy-linux-azure-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-azure-fips-v2 verification-needed-jammy-linux-azure-fips
Revision history for this message
Georgia Garcia (georgiag) wrote :

The mqueue patches are present in linux-azure-fips: commits 6e7ff802c7b10 and b4ebbcfebd4d3

tags: added: verification-done-jammy-linux-azure-fips
removed: verification-needed-jammy-linux-azure-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-mtk-v2 verification-needed-jammy-linux-mtk
Revision history for this message
Georgia Garcia (georgiag) wrote :

The mqueue patches are present in jammy-linux-mtk: commits 6e7ff802c7b10 and b4ebbcfebd4d3

tags: added: verification-done-jammy-linux-mtk
removed: verification-needed-jammy-linux-mtk
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-fips/5.15.0-1055.63+fips2 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-gcp-fips' to 'verification-done-jammy-linux-gcp-fips'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp-fips' to 'verification-failed-jammy-linux-gcp-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-gcp-fips-v2 verification-needed-jammy-linux-gcp-fips
Revision history for this message
Georgia Garcia (georgiag) wrote :

The mqueue patches are present in jammy-linux-gcp-fips: commits 6e7ff802c7b10 and b4ebbcfebd4d3

tags: added: verification-done-jammy-linux-gcp-fips
removed: verification-needed-jammy-linux-gcp-fips
Revision history for this message
John Chittum (jchittum) wrote :

Question -- this has landed in various jammy-5.15 kernels. This rolled downstream to the focal HWE kernels (specifically the cloud kernels)

1. was this intentional?
2. if so, could we add an affects for focal as well? it'll help us with tracking downstream dependency changes, specifically in livecd-rootfs:

https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789

Revision history for this message
John Johansen (jjohansen) wrote :

1. Yes. The backport was for 5.15 jammy kernels including HWE derivatives. The user space SRU was done in bug

  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146

which included Focal. The intent being Focal will only support mqueue if it is using and HWE kernel.

2. Yes that makes sense. I have added a linux-hwe entry for focal

Changed in linux-hwe (Ubuntu Jammy):
status: New → Invalid
Changed in linux (Ubuntu Focal):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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