Frederic Barrat writes:
>
> .. that one is more annoying.
> afu->phb == NULL?
Not sure how I missed that. Thanks for catching this Fred. I have sent a
v3 with the fix.
--
Vaibhav Jain
Linux Technology Center, IBM India Pvt. Ltd.
Le 22/11/2017 à 13:17, Vaibhav Jain a écrit :
During an eeh a kernel-oops is reported if no vPHB to allocated to the
typo, "to allocated". Not important, but
AFU. This happens as during AFU init, an error in creation of vPHB is
a non-fatal error. Hence afu->phb should always be checked
During an eeh a kernel-oops is reported if no vPHB to allocated to the
AFU. This happens as during AFU init, an error in creation of vPHB is
a non-fatal error. Hence afu->phb should always be checked for NULL
before iterating over it for the virtual AFU pci devices.
This patch fixes the kenel-oops
Vaibhav Jain writes:
> During an eeh a kernel-oops is reported if no vPHB to allocated to the
> AFU. This happens as during AFU init, an error in creation of vPHB is
> a non-fatal error. Hence afu->phb should always be checked for NULL
> before iterating over it for the virtual AFU pci devices.
>
During an eeh a kernel-oops is reported if no vPHB to allocated to the
AFU. This happens as during AFU init, an error in creation of vPHB is
a non-fatal error. Hence afu->phb should always be checked for NULL
before iterating over it for the virtual AFU pci devices.
This patch fixes the kenel-oops
