Public bug reported:
Description: s390/pci: Fix PCHID per port multi-function detection
Symptom: There are two cases in which PCI functions are incorrectly
placed, or not placed, in a shared PCI topology. In the first
case a PCI physical function (PF) which is initially in standby
was incorrectly not creating a new PCI topology when hotplugged,
but would if configured during boot. In the second case a PCI
virtual function (VF) would be placed in the shared PCI topology
of a PF if that PF is from the same card even if the parent PF
is not in the configuration which should lead the VF to be
isolated in its own single function topology.
Problem: Both problems are caused by logic bugs in the determination of
which PCI functions create topologies and when a PCI function
may be added to an existing topology.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-211738 severity-high
targetmilestone-inin---
** Tags added: architecture-s39064 bugnameltc-211738 severity-high
targetmilestone-inin---
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: 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/2104120
Title:
[Ubuntu 25.04] s390/pci: Fix PCHID per port multi-function detection
Status in linux package in Ubuntu:
New
Bug description:
Description: s390/pci: Fix PCHID per port multi-function detection
Symptom: There are two cases in which PCI functions are incorrectly
placed, or not placed, in a shared PCI topology. In the first
case a PCI physical function (PF) which is initially in standby
was incorrectly not creating a new PCI topology when
hotplugged,
but would if configured during boot. In the second case a PCI
virtual function (VF) would be placed in the shared PCI
topology
of a PF if that PF is from the same card even if the parent PF
is not in the configuration which should lead the VF to be
isolated in its own single function topology.
Problem: Both problems are caused by logic bugs in the determination of
which PCI functions create topologies and when a PCI function
may be added to an existing topology.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104120/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
