** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/2045384
Title:
AppArmor patch for mq-posix interface is missing in
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
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
The mqueue patches are present in jammy-linux-gcp-fips: commits
6e7ff802c7b10 and b4ebbcfebd4d3
** Tags removed: verification-needed-jammy-linux-gcp-fips
** Tags added: verification-done-jammy-linux-gcp-fips
--
You received this bug notification because you are a member of Kernel
Packages,
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
The mqueue patches are present in jammy-linux-mtk: commits 6e7ff802c7b10
and b4ebbcfebd4d3
** Tags removed: verification-needed-jammy-linux-mtk
** Tags added: verification-done-jammy-linux-mtk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
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
The mqueue patches are present in linux-azure-fips: commits
6e7ff802c7b10 and b4ebbcfebd4d3
** Tags removed: verification-needed-jammy-linux-azure-fips
** Tags added: verification-done-jammy-linux-azure-fips
--
You received this bug notification because you are a member of Kernel
Packages,
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
The mqueue patches are present in linux-nvidia-tegra: commits
6e7ff802c7b10 and b4ebbcfebd4d3
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
** Tags added: verification-done-jammy-linux-nvidia-tegra
--
You received this bug notification because you are a member of Kernel
I can confirm that the mqueue patches are present in linux-xilinx-
zynqmp: commits 6e7ff802c7b10 and b4ebbcfebd4d3
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are a
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
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
I could confirm that the patches are present in linux-bluefield and
linux-raspi: 6e7ff802c7b10 and b4ebbcfebd4d3
** Tags removed: verification-done-jammy-linux-azure
verification-needed-jammy-linux-bluefield verification-needed-jammy-linux-raspi
** Tags added:
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
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
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
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
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
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
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
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
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
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
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
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
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045384
Title:
AppArmor patch for mq-posix interface is
** Also affects: livecd-rootfs (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status:
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
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
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)
--
You received this bug notification because you are a member of Kernel
Packages,
Please use 22-hwe/stable if you can, please let us know if that's
acceptable.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- Issue: mq-posix interface does not work. It results in permission denied
- even all interfaces are connected.
+ [ Impact ]
- which ubuntu: UbuntuCore22 (kernel for Jammy)
+ mq-posix snapd interface does not work on Ubuntu Core 22. It results in
+ permission denied
32 matches
Mail list logo
