| 2022-01-13 08:38:11 |
Dmitrii Shcherbakov |
bug |
|
|
added bug |
| 2022-01-13 09:00:08 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Hirsute |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Hirsute) |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Focal |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Jammy) |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Impish |
|
| 2022-01-20 15:17:04 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Impish) |
|
| 2022-01-24 09:24:38 |
Po-Hsu Lin |
linux (Ubuntu Impish): status |
New |
Incomplete |
|
| 2022-01-24 09:24:40 |
Po-Hsu Lin |
linux (Ubuntu Focal): status |
New |
Incomplete |
|
| 2022-01-24 21:30:59 |
Dmitrii Shcherbakov |
linux (Ubuntu Focal): status |
Incomplete |
Confirmed |
|
| 2022-01-24 21:31:02 |
Dmitrii Shcherbakov |
linux (Ubuntu Impish): status |
Incomplete |
Confirmed |
|
| 2022-01-24 21:31:04 |
Dmitrii Shcherbakov |
linux (Ubuntu Jammy): status |
Incomplete |
Confirmed |
|
| 2022-01-24 21:31:08 |
Dmitrii Shcherbakov |
linux (Ubuntu Hirsute): status |
New |
Confirmed |
|
| 2022-01-25 04:36:24 |
Po-Hsu Lin |
description |
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16
Copied from patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested by Dmitrii Shcherbakov with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver.
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
|
| 2022-01-25 06:41:44 |
Po-Hsu Lin |
description |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16
Copied from patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested by Dmitrii Shcherbakov with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver.
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16
Copied from patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested by Dmitrii Shcherbakov with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver with certain operations (passing vlan 0).
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
|
| 2022-01-25 08:29:02 |
Po-Hsu Lin |
description |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16
Copied from patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested by Dmitrii Shcherbakov with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver with certain operations (passing vlan 0).
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on
Bluefield devices in kernels <=5.16
From patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it
requires some backport work on F/H due to they're missing commit
b55b3538 that split the legacy code out.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
passed with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver
with certain operations (setting vid 0). And other programs such as
libvirt that depends on this return value might be affected as well.
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
|
| 2022-01-25 08:29:04 |
Po-Hsu Lin |
linux (Ubuntu Focal): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-01-25 08:29:07 |
Po-Hsu Lin |
linux (Ubuntu Hirsute): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-01-25 08:29:09 |
Po-Hsu Lin |
linux (Ubuntu Jammy): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-01-25 08:29:11 |
Po-Hsu Lin |
linux (Ubuntu Impish): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-01-25 08:29:12 |
Po-Hsu Lin |
linux (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2022-01-25 08:29:14 |
Po-Hsu Lin |
linux (Ubuntu Hirsute): status |
Confirmed |
In Progress |
|
| 2022-01-25 08:29:15 |
Po-Hsu Lin |
linux (Ubuntu Impish): status |
Confirmed |
In Progress |
|
| 2022-01-25 08:29:18 |
Po-Hsu Lin |
linux (Ubuntu Jammy): status |
Confirmed |
In Progress |
|
| 2022-01-25 08:54:12 |
Po-Hsu Lin |
description |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on
Bluefield devices in kernels <=5.16
From patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it
requires some backport work on F/H due to they're missing commit
b55b3538 that split the legacy code out.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
passed with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver
with certain operations (setting vid 0). And other programs such as
libvirt that depends on this return value might be affected as well.
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
[Impact]
There is an issue with hypervisor host side mlx5 driver operation on
Bluefield devices in kernels <=5.16
From patch description:
When using libvirt to passthrough VF to VM it will always set the VF vlan
to 0 even if user didn’t request it, this will cause libvirt to fail to
boot in case the PF isn't eswitch owner.
Example of such case is the DPU host PF which isn't eswitch manager, so
any attempt to passthrough VF of it using libvirt will fail.
[Fix]
* 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
eswitch manager
This patch can be cherry-picked into Impish and newer kernels, but it
requires some backport work on F/H due to they're missing commit
b55b3538 that split the legacy code out.
The ESW_ALLOWED marco was later converted into a helper routine in
commit b16f2bb6.
[Test]
Test kernels can be found here:
F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/
Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
passed with positive feedback.
[Where problems could occur]
If this patch is erroneous, it might cause issue to this mlx5 driver
with certain operations (setting vid 0). And other programs such as
libvirt that depends on this return value might be affected as well.
[Original Bug Description]
There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37
It would be good to have this fix in Focal+ kernels.
This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. |
|
| 2022-01-26 16:00:50 |
Stefan Bader |
linux (Ubuntu Hirsute): status |
In Progress |
Won't Fix |
|
| 2022-01-26 16:01:30 |
Stefan Bader |
linux (Ubuntu Impish): importance |
Undecided |
Medium |
|
| 2022-01-26 16:01:30 |
Stefan Bader |
linux (Ubuntu Impish): status |
In Progress |
Fix Committed |
|
| 2022-01-26 16:01:39 |
Stefan Bader |
linux (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2022-01-26 16:45:32 |
Stefan Bader |
linux (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-01-31 17:24:09 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-impish |
|
| 2022-02-02 14:09:06 |
Ubuntu Kernel Bot |
tags |
verification-needed-impish |
verification-needed-focal verification-needed-impish |
|
| 2022-02-02 17:51:49 |
Dmitrii Shcherbakov |
tags |
verification-needed-focal verification-needed-impish |
verification-done-impish verification-needed-focal |
|
| 2022-02-02 18:22:40 |
Dmitrii Shcherbakov |
tags |
verification-done-impish verification-needed-focal |
verification-done-focal verification-done-impish |
|
| 2022-02-17 09:33:31 |
Launchpad Janitor |
linux (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-02-17 09:33:31 |
Launchpad Janitor |
cve linked |
|
2021-4083 |
|
| 2022-02-17 09:33:31 |
Launchpad Janitor |
cve linked |
|
2021-4155 |
|
| 2022-02-17 09:33:31 |
Launchpad Janitor |
cve linked |
|
2022-0330 |
|
| 2022-02-17 09:33:31 |
Launchpad Janitor |
cve linked |
|
2022-22942 |
|
| 2022-02-21 15:30:29 |
Launchpad Janitor |
linux (Ubuntu Impish): status |
Fix Committed |
Fix Released |
|
| 2022-05-20 10:56:45 |
Po-Hsu Lin |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
| 2022-05-20 10:56:47 |
Po-Hsu Lin |
linux (Ubuntu Jammy): status |
In Progress |
Fix Released |
|
