| 2019-11-20 14:19:38 |
bugproxy |
bug |
|
|
added bug |
| 2019-11-20 14:19:40 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2004 |
|
| 2019-11-20 14:19:41 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2019-11-20 14:19:44 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2019-11-20 14:19:45 |
bugproxy |
bug |
|
|
added subscriber CDE Administration |
| 2019-11-20 14:19:46 |
bugproxy |
bug |
|
|
added subscriber Heinz-Werner Seeck |
| 2019-11-20 14:19:48 |
bugproxy |
bug |
|
|
added subscriber Frank Heimes |
| 2019-11-20 14:19:50 |
bugproxy |
bug |
|
|
added subscriber Lou Peers |
| 2019-11-20 16:03:47 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2019-11-20 16:03:54 |
Frank Heimes |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-11-20 16:03:57 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Incomplete |
|
| 2019-11-20 16:04:01 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
Medium |
|
| 2019-11-20 16:04:07 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Frank Heimes (frank-heimes) |
|
| 2020-01-12 21:12:56 |
Paul Collins |
removed subscriber Lou Peers |
|
|
|
| 2020-01-28 09:12:27 |
Heinz-Werner Seeck |
summary |
[20.04 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
[20.10 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
|
| 2020-01-28 09:18:09 |
bugproxy |
tags |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2004 |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2010 |
|
| 2020-08-27 06:26:02 |
Heinz-Werner Seeck |
summary |
[20.10 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
[21.04 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
|
| 2020-08-27 06:27:50 |
bugproxy |
tags |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2010 |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2104 |
|
| 2021-02-23 08:55:10 |
Heinz-Werner Seeck |
summary |
[21.04 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
[21.10 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
|
| 2021-02-23 08:58:36 |
bugproxy |
tags |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2104 |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2110 |
|
| 2021-06-18 09:25:14 |
Frank Heimes |
bug |
|
|
added subscriber Boris Barth |
| 2021-09-01 13:20:09 |
bugproxy |
tags |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2110 |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2204 |
|
| 2021-09-01 14:12:17 |
Frank Heimes |
summary |
[21.10 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
[22.04 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
|
| 2022-09-20 15:40:43 |
Frank Heimes |
ubuntu-z-systems: status |
Incomplete |
New |
|
| 2022-09-20 15:40:47 |
Frank Heimes |
linux (Ubuntu): status |
Incomplete |
New |
|
| 2022-09-20 15:40:58 |
Frank Heimes |
ubuntu-z-systems: assignee |
Frank Heimes (fheimes) |
Skipper Bug Screeners (skipper-screen-team) |
|
| 2022-09-20 15:41:01 |
Frank Heimes |
linux (Ubuntu): assignee |
Skipper Bug Screeners (skipper-screen-team) |
Frank Heimes (fheimes) |
|
| 2022-09-21 05:50:09 |
Frank Heimes |
summary |
[22.04 FEAT] Enhanced Interpretation for PCI Functions - kernel part |
[22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part |
|
| 2022-09-21 05:59:46 |
Frank Heimes |
linux (Ubuntu): importance |
Undecided |
Medium |
|
| 2022-09-21 05:59:58 |
Frank Heimes |
linux (Ubuntu): assignee |
Frank Heimes (fheimes) |
Canonical Kernel Team (canonical-kernel-team) |
|
| 2022-09-21 06:00:04 |
Frank Heimes |
linux (Ubuntu): status |
New |
In Progress |
|
| 2022-09-21 06:00:08 |
Frank Heimes |
ubuntu-z-systems: status |
New |
In Progress |
|
| 2022-09-21 06:00:12 |
Frank Heimes |
information type |
Private |
Public |
|
| 2022-10-03 07:25:42 |
Frank Heimes |
linux (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2022-10-03 07:25:46 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2022-10-04 09:44:59 |
Launchpad Janitor |
linux (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2022-10-04 09:44:59 |
Launchpad Janitor |
cve linked |
|
2022-2978 |
|
| 2022-10-04 10:48:28 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
| 2023-05-17 14:31:24 |
bugproxy |
attachment added |
|
backport of c435c54639aa vfio/pci: introduce CONFIG_VFIO_PCI_ZDEV_KVM https://bugs.launchpad.net/bugs/1853306/+attachment/5673572/+files/0001-vfio-pci-introduce-CONFIG_VFIO_PCI_ZDEV_KVM.patch |
|
| 2023-05-17 14:31:26 |
bugproxy |
attachment added |
|
<backport of 09340b2fca00 KVM: s390: pci: add routines to start/stop interpretive execution> https://bugs.launchpad.net/bugs/1853306/+attachment/5673573/+files/0002-KVM-s390-pci-add-routines-to-start-stop-interpretive.patch |
|
| 2023-05-17 14:31:28 |
bugproxy |
attachment added |
|
backport of 8061d1c31f1a vfio-pci/zdev: add open/close device hooks https://bugs.launchpad.net/bugs/1853306/+attachment/5673574/+files/0003-vfio-pci-zdev-add-open-close-device-hooks.patch |
|
| 2023-05-17 14:40:16 |
bugproxy |
attachment added |
|
backport of db1c875e0539 KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices https://bugs.launchpad.net/bugs/1853306/+attachment/5673575/+files/0004-KVM-s390-add-KVM_S390_ZPCI_OP-to-manage-guest-zPCI-d.patch |
|
| 2023-05-17 14:40:18 |
bugproxy |
attachment added |
|
backport of ca922fecda6c KVM: s390: pci: Hook to access KVM lowlevel from VFIO https://bugs.launchpad.net/bugs/1853306/+attachment/5673576/+files/0005-KVM-s390-pci-Hook-to-access-KVM-lowlevel-from-VFIO.patch |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
nominated for series |
|
Ubuntu Mantic |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
bug task added |
|
linux (Ubuntu Mantic) |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
bug task added |
|
linux (Ubuntu Lunar) |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-06-07 08:16:10 |
Frank Heimes |
bug task added |
|
linux (Ubuntu Jammy) |
|
| 2023-06-07 08:16:21 |
Frank Heimes |
linux (Ubuntu Lunar): status |
New |
Fix Released |
|
| 2023-06-07 08:16:28 |
Frank Heimes |
linux (Ubuntu Kinetic): status |
New |
Won't Fix |
|
| 2023-06-07 08:16:35 |
Frank Heimes |
linux (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-06-13 19:22:26 |
Frank Heimes |
attachment added |
|
0000-pull.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853306/+attachment/5679544/+files/0000-pull.patch |
|
| 2023-06-14 15:34:25 |
Frank Heimes |
description |
The PCI Passthrough implementation is based on intercepting PCI I/O instructions which leads to a reduced I/O performance compared to execution of PCI instructions in LPAR.
For improved performance the interpretive execution of the PCI store and PCI load instructions get enabled.
Further improvement is achieved by enabling the Adapter-Event-Notification |
[ Impact ]
* Currently the PCI passthrough implementation for s390x is based on
intercepting PCI I/O instructions, which leads to a reduced I/O performance
compared to the execution of PCI instructions directly in LPAR.
* Hence users may face I/O bottlenecks when using PCI devices in passthrough
mode based on the current implementation.
* For avoiding this and to improve performance, the interpretive execution
of the PCI store and PCI load instructions get enabled.
* A further improvement is achieved by enabling the Adapter-Event-Notification
Interpretation (AENI).
* Since LTS releases are the main focus for stable and long running KVM
workloads, it is highly desired to get this backported to the jammy kernel
(and because the next LTS is still some time away).
[ Test Plan ]
* Have an Ubuntu Server 22.04 installation on LPAR,
that is able to access (ideally multiple) PCI devices,
like RoCE Express (network) or NVMe disks.
* Setup KVM and pass through (ideally multiple) of these PCI devices
(that are otherwise unused on the KVM host).
* Generate IO load on these passed through PCI devices,
for example with stress-ng, using class network and/or device
and/or io stressors.
* This PR also introduces a new kernel config option 'VFIO_PCI_ZDEV_KVM'
that allows to enable support for the s390x-specific extensions and
enhancements to KVM passthrough, such as interpretive execution of zPCI
instructions and is with this PR and got enabled.
* The qemu autopkgtest (also needed due to LP#1853307) will be a got fit
to identify any potential regressions, also in the kvm kernel area.
* zPCI passthrough related test will be done by IBM.
[ Where problems could occur ]
* The modifications do not change the way users or APIs have to make
use of PCI passthrough, only the internal implementation got modified.
* The vast majority of the code changes/or additional code is s390x-specific,
under arch/s390 and drivers/s390.
* However there is also common code touched:
* 'kvm: use kvfree() in kvm_arch_free_vm()' touches
arch/arm64/include/asm/kvm_host.h, arch/arm64/kvm/arm.c,
arch/x86/include/asm/kvm_host.h, arch/x86/kvm/x86.c,
include/linux/kvm_host.h switches in kvm_arch_free_vm() from kfree() to
kvfree() allowing to use the common variant, which is upstream since v5.16
and with that well established.
* And 'vfio-pci/zdev: add open/close device hooks' touches
drivers/vfio/pci/vfio_pci_core.c and drivers/vfio/pci/vfio_pci_zdev.c
include/linux/vfio_pci_core.h add now code to introduce device hooks.
It's upstream since kernel 6.0.
* 'KVM: s390: pci: provide routines for en-/disabling interrupt forwarding'
expands a single #if statement in include/linux/sched/user.h.
* 'KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices'
adds s390x specific KVM_S390_ZPCI_OP and it's definition to
include/uapi/linux/kvm.h.
* And 'vfio-pci/zdev: different maxstbl for interpreted devices' and
'vfio-pci/zdev: add function handle to clp base capability' expand
s390x-specific (aka z-specific aka zdev) device structs in
include/uapi/linux/vfio_zdev.h.
* This shows that the vast majority of modifications are s390x specific,
even in most of the common code files.
* The remaining modifications in the (generally) common code files are
related to the newly introduced kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'
and documentation.
* The s390x changes are more significant, and could not only harm
passthrough itself for zPCI devices, but also KVM virtualization in general.
* In addition to these kernel changes, qemu modifications are needed
as well (that are addressed at LP#1853307), this modified kernel
must be tested in combination with the updated qemu package.
- The qemu autopkgtest will be a got fit to identify any regressions,
also in the kernel.
- In addition some passthrough related test will be done by IBM
__________
The PCI Passthrough implementation is based on intercepting PCI I/O instructions which leads to a reduced I/O performance compared to execution of PCI instructions in LPAR.
For improved performance the interpretive execution of the PCI store and PCI load instructions get enabled.
Further improvement is achieved by enabling the Adapter-Event-Notification |
|
| 2023-06-14 15:53:47 |
Frank Heimes |
linux (Ubuntu Jammy): assignee |
|
Canonical Kernel Team (canonical-kernel-team) |
|
| 2023-07-07 13:35:47 |
Roxana Nicolescu |
linux (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-07-13 08:42:07 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 severity-high targetmilestone-inin2204 |
architecture-s39064 bugnameltc-182254 kernel-spammed-jammy-linux severity-high targetmilestone-inin2204 verification-needed-jammy |
|
| 2023-07-18 14:29:49 |
Frank Heimes |
description |
[ Impact ]
* Currently the PCI passthrough implementation for s390x is based on
intercepting PCI I/O instructions, which leads to a reduced I/O performance
compared to the execution of PCI instructions directly in LPAR.
* Hence users may face I/O bottlenecks when using PCI devices in passthrough
mode based on the current implementation.
* For avoiding this and to improve performance, the interpretive execution
of the PCI store and PCI load instructions get enabled.
* A further improvement is achieved by enabling the Adapter-Event-Notification
Interpretation (AENI).
* Since LTS releases are the main focus for stable and long running KVM
workloads, it is highly desired to get this backported to the jammy kernel
(and because the next LTS is still some time away).
[ Test Plan ]
* Have an Ubuntu Server 22.04 installation on LPAR,
that is able to access (ideally multiple) PCI devices,
like RoCE Express (network) or NVMe disks.
* Setup KVM and pass through (ideally multiple) of these PCI devices
(that are otherwise unused on the KVM host).
* Generate IO load on these passed through PCI devices,
for example with stress-ng, using class network and/or device
and/or io stressors.
* This PR also introduces a new kernel config option 'VFIO_PCI_ZDEV_KVM'
that allows to enable support for the s390x-specific extensions and
enhancements to KVM passthrough, such as interpretive execution of zPCI
instructions and is with this PR and got enabled.
* The qemu autopkgtest (also needed due to LP#1853307) will be a got fit
to identify any potential regressions, also in the kvm kernel area.
* zPCI passthrough related test will be done by IBM.
[ Where problems could occur ]
* The modifications do not change the way users or APIs have to make
use of PCI passthrough, only the internal implementation got modified.
* The vast majority of the code changes/or additional code is s390x-specific,
under arch/s390 and drivers/s390.
* However there is also common code touched:
* 'kvm: use kvfree() in kvm_arch_free_vm()' touches
arch/arm64/include/asm/kvm_host.h, arch/arm64/kvm/arm.c,
arch/x86/include/asm/kvm_host.h, arch/x86/kvm/x86.c,
include/linux/kvm_host.h switches in kvm_arch_free_vm() from kfree() to
kvfree() allowing to use the common variant, which is upstream since v5.16
and with that well established.
* And 'vfio-pci/zdev: add open/close device hooks' touches
drivers/vfio/pci/vfio_pci_core.c and drivers/vfio/pci/vfio_pci_zdev.c
include/linux/vfio_pci_core.h add now code to introduce device hooks.
It's upstream since kernel 6.0.
* 'KVM: s390: pci: provide routines for en-/disabling interrupt forwarding'
expands a single #if statement in include/linux/sched/user.h.
* 'KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices'
adds s390x specific KVM_S390_ZPCI_OP and it's definition to
include/uapi/linux/kvm.h.
* And 'vfio-pci/zdev: different maxstbl for interpreted devices' and
'vfio-pci/zdev: add function handle to clp base capability' expand
s390x-specific (aka z-specific aka zdev) device structs in
include/uapi/linux/vfio_zdev.h.
* This shows that the vast majority of modifications are s390x specific,
even in most of the common code files.
* The remaining modifications in the (generally) common code files are
related to the newly introduced kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'
and documentation.
* The s390x changes are more significant, and could not only harm
passthrough itself for zPCI devices, but also KVM virtualization in general.
* In addition to these kernel changes, qemu modifications are needed
as well (that are addressed at LP#1853307), this modified kernel
must be tested in combination with the updated qemu package.
- The qemu autopkgtest will be a got fit to identify any regressions,
also in the kernel.
- In addition some passthrough related test will be done by IBM
__________
The PCI Passthrough implementation is based on intercepting PCI I/O instructions which leads to a reduced I/O performance compared to execution of PCI instructions in LPAR.
For improved performance the interpretive execution of the PCI store and PCI load instructions get enabled.
Further improvement is achieved by enabling the Adapter-Event-Notification |
[ Impact ]
* Currently the PCI passthrough implementation for s390x is based on
intercepting PCI I/O instructions, which leads to a reduced I/O performance
compared to the execution of PCI instructions directly in LPAR.
* Hence users may face I/O bottlenecks when using PCI devices in passthrough
mode based on the current implementation.
* For avoiding this and to improve performance, the interpretive execution
of the PCI store and PCI load instructions get enabled.
* A further improvement is achieved by enabling the Adapter-Event-Notification
Interpretation (AENI).
* Since LTS releases are the main focus for stable and long running KVM
workloads, it is highly desired to get this backported to the jammy kernel
(and because the next LTS is still some time away).
[ Test Plan ]
* Hardware used: z14 or greater LPAR, PCI-attached devices
(RoCE VFs, ISM devices, NVMe drive)
* Setup: Both the kernel and QEMU features are needed for the feature
to function (an upstream QEMU can be used to verify the kernel early),
and the facility is only avaialble on z14 or newer.
When any of those pieces is missing,
the interpretation facility will not be used.
When both the kernel and QEMU features are included in their respective
packages, and running in an LPAR on a z14 or newer machine,
this feature will be enabled automatically.
Existing supported devices should behave as before with no changes
required by an end-user (e.g. no changes to libvirt domain definitions)
-- but will now make use of the interpretation facility.
Additionally, ISM devices will now be eligible for vfio-pci passthrough
(where before QEMU would exit on error if attempting to provide an ISM
device for vfio-pci passthrough, preventing the guest from starting)
* Testing will include the following scenarios, repeated each for RoCE,
ISM and NVMe:
1) Testing of basic device passthrough (create a VM with a vfio-pci
device as part of the libvirt domain definition, passing through
a RoCE VF, an ISM device, or an NVMe drive. Verify that the device
is available in the guest and functioning)
2) Testing of device hotplug/unplug (create a VM with a vfio-pci device,
virsh detach-device to remove the device from the running guest,
verify the device is removed from the guest, then virsh attach-device
to hotplug the device to the guest again, verify the device functions
in the guest)
3) Host power off testing: Power off the device from the host, verify
that the device is unplugged from the guest as part of the poweroff
4) Guest power off testing: Power off the device from within the guest,
verify that the device is unusuable in the guest,
power the device back on within the guest and verify that the device
is once again usable.
5) Guest reboot testing: (create a VM with a vfio-pci device,
verify the device is in working condition, reboot the guest,
verify that the device is still usable after reboot)
Testing will include the following scenarios specifically for ISM devices:
1) Testing of SMC-D v1 fallback: Using 2 ISM devices on the same VCHID
that share a PNETID, create 2 guests and pass one ISM device
via vfio-pci device to each guest.
Establish TCP connectivity between the 2 guests using the libvirt
default network, and then use smc_run
(https://manpages.ubuntu.com/manpages/jammy/man8/smc_run.8.html)
to run an iperf workload between the 2 guests (will include both
short workloads and longer-running workloads).
Verify that SMC-D transfer was used between the guests instead
of TCP via 'smcd stats'
(https://manpages.ubuntu.com/manpages/jammy/man8/smcd.8.html)
2) Testing of SMC-D v2: Same as above,
but using 2 ISM devices on the same VCHID that have no PNETID specified
Testing will include the following scenarios specifically for RoCE devices:
1) Ping testing: Using 2 RoCE VFs that share a common network,
create 2 guests and pass one RoCE device to each guest.
Assign IP addresses within each guest to the associated TCP interface,
perform a ping between the guests to verify connectivity.
2) Iperf testing: Similar to the above, but instead establish an iperf
connection between the 2 guests and verify that the workload
is successful / no errors.
Will include both short workloads and longer-running workloads.
Testing will include the following scenario specifically for NVMe devices:
1) Fio testing: Using a NVMe drive passed to the guest via vfio-pci,
run a series of fio tests against the device from within the guest,
verifying that the workload is successful / no errors.
Will include both short workloads and longer-running workloads.
[ Where problems could occur ]
* The modifications do not change the way users or APIs have to make
use of PCI passthrough, only the internal implementation got modified.
* The vast majority of the code changes/or additional code is s390x-specific,
under arch/s390 and drivers/s390.
* However there is also common code touched:
* 'kvm: use kvfree() in kvm_arch_free_vm()' touches
arch/arm64/include/asm/kvm_host.h, arch/arm64/kvm/arm.c,
arch/x86/include/asm/kvm_host.h, arch/x86/kvm/x86.c,
include/linux/kvm_host.h switches in kvm_arch_free_vm() from kfree() to
kvfree() allowing to use the common variant, which is upstream since v5.16
and with that well established.
* And 'vfio-pci/zdev: add open/close device hooks' touches
drivers/vfio/pci/vfio_pci_core.c and drivers/vfio/pci/vfio_pci_zdev.c
include/linux/vfio_pci_core.h add now code to introduce device hooks.
It's upstream since kernel 6.0.
* 'KVM: s390: pci: provide routines for en-/disabling interrupt forwarding'
expands a single #if statement in include/linux/sched/user.h.
* 'KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices'
adds s390x specific KVM_S390_ZPCI_OP and it's definition to
include/uapi/linux/kvm.h.
* And 'vfio-pci/zdev: different maxstbl for interpreted devices' and
'vfio-pci/zdev: add function handle to clp base capability' expand
s390x-specific (aka z-specific aka zdev) device structs in
include/uapi/linux/vfio_zdev.h.
* This shows that the vast majority of modifications are s390x specific,
even in most of the common code files.
* The remaining modifications in the (generally) common code files are
related to the newly introduced kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'
and documentation.
* The s390x changes are more significant, and could not only harm
passthrough itself for zPCI devices, but also KVM virtualization in general.
* In addition to these kernel changes, qemu modifications are needed
as well (that are addressed at LP#1853307), this modified kernel
must be tested in combination with the updated qemu package.
- The qemu autopkgtest will be a got fit to identify any regressions,
also in the kernel.
- In addition some passthrough related test will be done by IBM
__________
The PCI Passthrough implementation is based on intercepting PCI I/O instructions which leads to a reduced I/O performance compared to execution of PCI instructions in LPAR.
For improved performance the interpretive execution of the PCI store and PCI load instructions get enabled.
Further improvement is achieved by enabling the Adapter-Event-Notification |
|
| 2023-07-20 18:00:46 |
bugproxy |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-jammy-linux severity-high targetmilestone-inin2204 verification-needed-jammy |
architecture-s39064 bugnameltc-182254 kernel-spammed-jammy-linux severity-high targetmilestone-inin2204 verification-done-jammy |
|
| 2023-08-08 16:00:45 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-jammy-linux severity-high targetmilestone-inin2204 verification-done-jammy |
architecture-s39064 bugnameltc-182254 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-needed-jammy |
|
| 2023-08-08 16:01:35 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-needed-jammy |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-jammy |
|
| 2023-08-08 16:01:36 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-jammy |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-jammy |
|
| 2023-08-08 16:38:35 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-needed-focal verification-needed-jammy |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2022-48502 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-0597 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-2124 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3090 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-31248 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3141 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3389 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3390 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-3439 |
|
| 2023-08-14 06:47:41 |
Launchpad Janitor |
cve linked |
|
2023-35001 |
|
| 2023-08-22 18:56:49 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-jammy-linux-aws |
|
| 2023-08-26 20:11:41 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-jammy-linux-aws |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure |
|
| 2023-09-01 14:40:49 |
bugproxy |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-jammy-linux-aws |
|
| 2023-09-09 14:16:52 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-jammy-linux-aws |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws |
|
| 2023-10-03 20:41:41 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-xilinx-zynqmp |
|
| 2023-10-04 07:16:50 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-jammy verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-xilinx-zynqmp |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-jammy-linux-aws verification-done-jammy-linux-xilinx-zynqmp |
|
| 2024-03-01 06:16:00 |
Ubuntu Kernel Bot |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-jammy-linux-aws verification-done-jammy-linux-xilinx-zynqmp |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-jammy-linux-aws verification-done-jammy-linux-xilinx-zynqmp verification-needed-jammy-linux-mtk |
|
| 2024-03-01 07:46:14 |
Frank Heimes |
tags |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-jammy-linux-aws verification-done-jammy-linux-xilinx-zynqmp verification-needed-jammy-linux-mtk |
architecture-s39064 bugnameltc-182254 kernel-spammed-focal-linux-aws-5.15-v2 kernel-spammed-focal-linux-nvidia-tegra-5.15 kernel-spammed-jammy-linux kernel-spammed-jammy-linux-aws-v2 kernel-spammed-jammy-linux-azure-v2 kernel-spammed-jammy-linux-mtk-v2 kernel-spammed-jammy-linux-nvidia-tegra kernel-spammed-jammy-linux-nvidia-tegra-igx kernel-spammed-jammy-linux-xilinx-zynqmp-v2 severity-high targetmilestone-inin2204 verification-done-focal verification-done-focal-linux-aws-5.15 verification-done-jammy verification-done-jammy-linux-aws verification-done-jammy-linux-mtk verification-done-jammy-linux-xilinx-zynqmp |
|
