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
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+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
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1019.19~20.04.1 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-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1006.6 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-
igx' to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1025.29 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-gcp-tcpx/5.15.0-1002.2
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-focal-linux-gcp-tcpx' to 'verification-done-
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1019.19 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
This bug is awaiting verification that the linux-
oracle-6.2/6.2.0-1015.15~22.04.1 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-
oracle-6.2' to
This bug was fixed in the package linux - 5.4.0-166.183
---
linux (5.4.0-166.183) focal; urgency=medium
* focal/linux: 5.4.0-166.183 -proposed tracker (LP: #2038010)
* Use new annotations model (LP: #2019000)
- [Packaging] new annotations model infrastructure
-
This bug is awaiting verification that the linux-
bluefield/5.15.0-1029.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-bluefield' to
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1044.50 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
This bug is awaiting verification that the linux-intel-iot-
realtime/5.15.0-1042.44 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-iot-
realtime' to
This bug is awaiting verification that the linux-
starfive-6.2/6.2.0-1008.9~22.04.1 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-
starfive-6.2' to
This bug was fixed in the package linux - 5.15.0-88.98
---
linux (5.15.0-88.98) jammy; urgency=medium
* jammy/linux: 5.15.0-88.98 -proposed tracker (LP: #2038055)
* CVE-2023-4244
- netfilter: nf_tables: don't skip expired elements during walk
- netfilter: nf_tables:
This bug is awaiting verification that the linux-iot/5.4.0-1025.26
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-focal-linux-iot' to 'verification-done-focal-
linux-iot'. If the
This bug is awaiting verification that the linux-gkeop/5.15.0-1032.38
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-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug is awaiting verification that the linux-raspi/5.15.0-1042.45
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 is awaiting verification that the linux-riscv/6.2.0-36.37.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
This bug was fixed in the package linux - 6.2.0-36.37
---
linux (6.2.0-36.37) lunar; urgency=medium
* lunar/linux: 6.2.0-36.37 -proposed tracker (LP: #2038076)
* Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
(LP: #2035181)
- selftests/bpf: fix
This bug is awaiting verification that the linux-oracle/6.2.0-1015.15
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-lunar-linux-oracle' to 'verification-done-
lunar-linux-oracle'.
So it looks like this patch was applied to linux/5.4.0-166.183,
linux/5.15.0-88.98, and linux/6.2.0-36.37, but I'm not seeing a request
for verification on the jammy-azure-5.15.0-1049 kernel series, and it
looks like linux-azure (5.15.0-1049.56) does not include the fix. Can we
get the azure
I verified the issue on kernel linux/5.4.0-166.183, linux/5.15.0-88.98
and linux/6.2.0-36.37 and the issue is fixed. I was able to run enclave
in debug mode in all 3 kernels.
** Tags removed: verification-needed-lunar-linux
** Tags added: verification-done-lunar-linux
--
You received this bug
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
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/2034745
Title:
[regression] Unable to
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
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/2034745
Title:
[regression] Unable to
This bug is awaiting verification that the linux/6.2.0-36.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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-166.183 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-88.98 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
This also affects 5.4.0 from 5.4.0-158 on. Is this version getting a
fix? It's not clear to me from the linked thread which kernel versions
are getting fixes, given that focal supports both 5.4 and 5.15 kernels.
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Lunar)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In
Reposted the patch for all affected kernels:
https://lists.ubuntu.com/archives/kernel-team/2023-September/142913.html
--
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/2034745
Title:
FWIW, this not only affects the 5.15/jammy kernel series, but also at
least 6.2/lunar: https://github.com/openzfs/zfs/issues/15223 , and also
affects non-SGX use cases like OpenZFS features that benefit from AVX
support (raidz, encryption, ..)
** Bug watch added: github.com/openzfs/zfs/issues
Patch submitted for review https://lists.ubuntu.com/archives/kernel-
team/2023-September/142739.html
--
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/2034745
Title:
[regression] Unable to
Thanks Gaurav
--
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/2034745
Title:
[regression] Unable to initialize SGX enclaves with XFRM other than 3
Status in linux package in Ubuntu:
I tested the changes today and was able to successfully run enclave in
debug mode. Thanks a lot Tim.
--
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/2034745
Title:
[regression] Unable to
** Description changed:
SRU Justification
[Impact]
In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
sgx_encl_init returns EINVAL. The only reason this wouldn't work
properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine
in 5.15.0-1043.
Likely
** Description changed:
+ SRU Justification
+
+ [Impact]
+
In 5.15.0-1045, only loading enclaves with XFRM set to 3 works,
sgx_encl_init returns EINVAL. The only reason this wouldn't work
properly is if sgx_drv_init thinks XSAVE isn't enabled. This works fine
in 5.15.0-1043.
Likely
** Package changed: linux-azure (Ubuntu) => linux (Ubuntu)
--
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/2034745
Title:
[regression] Unable to initialize SGX enclaves with XFRM other
Please try the referenced kernel jammy-
azure-5.15.0-1049.56~lp2034745.1.tgz with the fix commit. Note that this
kernel is not signed for a UEFI secure boot environment.
** Attachment added: "Test kernel"
https://kernel.ubuntu.com/~rtg/jammy-sgx-xsave-lp2034745/5.15.0-1049.56~lp2034745.1/
--
** Package changed: linux-signed-azure-5.15 (Ubuntu) => linux-azure
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2034745
Title:
[regression] Unable to initialize SGX
40 matches
Mail list logo
