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 is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1021.25 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
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-aws/5.19.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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.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-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-ibm/5.19.0-1021.23
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-gcp - 5.19.0-1020.22
---
linux-gcp (5.19.0-1020.22) kinetic; urgency=medium
* kinetic/linux-gcp: 5.19.0-1020.22 -proposed tracker (LP: #2011863)
* Miscellaneous Ubuntu changes
- [config] Enable CONFIG_TDX_GUEST_DRIVER=m
-
This bug was fixed in the package linux - 5.19.0-40.41
---
linux (5.19.0-40.41) kinetic; urgency=medium
* kinetic/linux: 5.19.0-40.41 -proposed tracker (LP: #2012668)
* CVE-2023-0468
- io_uring: fix tw losing poll events
- io_uring: make poll refs more robust
*
Is there a separate bug tracking for focal? I am seeing this issue in focal as
well. Kernel 5.15.0-1035-azure
Attached is a single log.txt file that has both the journal log and cloud-init
log
** Attachment added: "logs.zip"
There is no action needed from a cloud-init point of view, and we do not
see our integration test failing anymore regarding this issue. Daily
cloud images seem to contain the patched kernel. Marking this as invalid
for cloud-init.
** Changed in: cloud-init (Ubuntu Jammy)
Status: Confirmed
This bug is awaiting verification that the linux-azure/5.15.0-1036.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,
This bug is awaiting verification that the linux/5.19.0-40.41 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 was fixed in the package linux - 5.15.0-69.76
---
linux (5.15.0-69.76) jammy; urgency=medium
* jammy/linux: 5.15.0-69.76 -proposed tracker (LP: #2012092)
* NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 (LP: #2009325)
- NFS: Correct timing for
The issue is also present in Jammy distro kernel (linux-
image-5.15.0-67-generic) and e2fsprofs 1.46.5-2ubuntu1.1
How to reproduce :
* Create an openstack instance and user virtio-scsi as block device controller
* Add a Cinder volume (backed by PureStorage/iSCSI)
* format the whole volume :
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2003816
Title:
Regression in ext4 during online
** Changed in: linux-gcp (Ubuntu Kinetic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2003816
Title:
Regression in ext4 during online resize
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in
Released with jammy/linux-azure 5.15.0-1035.42
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
Released with jammy/linux-aws 5.15.0-1032.36
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2003816
The issue has been observed with 5.19 kernels on Amazon and Azure
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Kinetic)
>From cloud-init perspective, we have seen this too in our CI/CD
integration runs on both GCP and Azure lunar daily images which allows
cloud-init to resize2fs /dev/root on first boot, but also re-invokes
resize2fs a second time to assert cloud-init can be re-run all boot
stages without having to
Added linux-azure task here too to track that it also affects that
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2003816
Title:
Regression in ext4 during online resize
FYI, bit of a necro -- we're seeing this currently on the 20.04 5.15
kernel and the 23.04 5.19 kernel. I haven't checked on the proposed 6.2
kernel yet.
this can be reproduced on AWS
Reproduction step:
1. Create an AWS instance with AMI `ami-056a67ea1b8ffa0fc` (Linux
5.15.0-1022-aws) in
This looks to have been picked into derivative 5.15 kernels and verified
there already. So I am taking that as base for the distro kernel fix.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of
This bug is awaiting verification that the linux/5.15.0-68.75 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 was fixed in the package linux-gcp - 5.15.0-1030.37
---
linux-gcp (5.15.0-1030.37) jammy; urgency=medium
* jammy/linux-gcp: 5.15.0-1030.37 -proposed tracker (LP: #2004313)
* Jammy update: v5.15.81 upstream stable release (LP: #2003130)
- [Config] updateconfigs for
Verified the issue is no longer reproducible on linux-aws Ubuntu-
aws-5.15.0-1031.35
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
This bug is awaiting verification that the linux-gkeop/5.15.0-1016.21
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-gke/5.15.0-1028.33
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-gcp/5.15.0-1030.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' to 'verification-done-jammy'. If the
problem still exists,
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-gcp (Ubuntu)
Status: New => Invalid
This bug is awaiting verification that the linux-aws/5.15.0-1031.35
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 (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
36 matches
Mail list logo
