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-
aws-5.15/5.15.0-1046.51~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-
aws-5.15' to
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1019.19
---
linux-oem-6.0 (6.0.0-1019.19) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1019.19 -proposed tracker (LP: #2024151)
* CVE-2023-2430
- io_uring: get rid of double locking
- io_uring: extract a
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2015956
Title:
selftest: fib_tests: Always
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1033.34
---
linux-oem-5.17 (5.17.0-1033.34) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1033.34 -proposed tracker (LP:
#2019421)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
-
Verified with:
linux-aws/5.19.0-1027.28
linux-aws/5.15.0-1038.43
linux-azure/5.15.0-1040.47
linux-azure/5.19.0-1028.31
linux-oem-5.17/5.17.0-1033.34
For
linux-aws/5.4.0-1104.112
linux-azure/5.4.0-1110.116
The fib_test.sh script is still missing, I cannot verify it at this point.
** Tags
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1033.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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1028.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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.4.0-1110.116
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' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.4.0-1104.112
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' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1040.47
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1038.43
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' to 'verification-done-jammy'. If the
problem still exists,
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug is awaiting verification that the linux-aws/5.19.0-1027.28
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-kinetic' to 'verification-done-kinetic'. If the
problem still
Verified with linux-gcp/5.19.0-1024.26 linux-
riscv-5.15/5.15.0-1034.38~20.04.1 linux-allwinner/5.19.0-1012.12
linux/5.15.0-72.79
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-jammy
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1031.36 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-bluefield/5.4.0-1064.70
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' to 'verification-done-focal'. If the
problem still
This bug was fixed in the package linux - 5.4.0-149.166
---
linux (5.4.0-149.166) focal; urgency=medium
* focal/linux: 5.4.0-149.166 -proposed tracker (LP: #2016591)
* Focal update: v5.4.233 upstream stable release (LP: #2015909)
- dma-mapping: add generic helpers for
This bug is awaiting verification that the linux-
allwinner/5.19.0-1012.12 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-kinetic' to 'verification-
done-kinetic'. If the problem
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1034.38~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-gcp/5.19.0-1024.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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug was fixed in the package linux - 5.19.0-42.43
---
linux (5.19.0-42.43) kinetic; urgency=medium
* kinetic/linux: 5.19.0-42.43 -proposed tracker (LP: #2016503)
* selftest: fib_tests: Always cleanup before exit (LP: #2015956)
- selftest: fib_tests: Always cleanup
This bug was fixed in the package linux - 5.15.0-72.79
---
linux (5.15.0-72.79) jammy; urgency=medium
* jammy/linux: 5.15.0-72.79 -proposed tracker (LP: #2016548)
* Add split lock detection for EMR (LP: #2015855)
- x86/split_lock: Enumerate architectural split lock disable
Verified with focal linux/5.4.0-149.166, test passed. Also checked with
F-kvm, it will fail with "Error: Unknown device type." as expected.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1010.10 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' to
'verification-done-jammy'. If the problem still
This bug is awaiting verification that the linux/5.15.0-72.79 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' to 'verification-done-jammy'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.19.0-41.42 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.4.0-149.166 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' to 'verification-done-focal'. If the problem
still exists, change
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix
https://lists.ubuntu.com/archives/kernel-team/2023-April/138657.html
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu)
Importance:
** Description changed:
- [Impact]
+ [Impact]
(Cpoied from commit message)
Usage of `set -e` before executing a command causes immediate exit
on failure, without cleanup up the resources allocated at setup.
This can affect the next tests that use the same resources,
leading to a chain
31 matches
Mail list logo
