Bug 2074317

Summary:	genirq/affinity: Consider that CPUs on nodes can be unbalanced
Product:	Red Hat Enterprise Linux 8	Reporter:	Ming Lei <minlei>
Component:	kernel	Assignee:	Ming Lei <minlei>
kernel sub component:	Kernel-Core	QA Contact:	ChanghuiZhong <czhong>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	kernel-qe
Version:	8.7	Keywords:	Bugfix, Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kernel-4.18.0-391.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2074315	Environment:
Last Closed:	2022-11-08 10:28:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2074315
Bug Blocks:

Description Ming Lei 2022-04-12 00:24:02 UTC

+++ This bug was initially created as a clone of Bug #2074315 +++

Description of problem:

https://lore.kernel.org/lkml/164966454348.4207.142052541335966473.tip-bot2@tip-bot2/

genirq/affinity: Consider that CPUs on nodes can be unbalanced

If CPUs on a node are offline at boot time, the number of nodes is
different when building affinity masks for present cpus and when building
affinity masks for possible cpus. This causes the following problem:

In the case that the number of vectors is less than the number of nodes
there are cases where bits of masks for present cpus are overwritten when
building masks for possible cpus.

Fix this by excluding CPUs, which are not part of the current build mask
(present/possible).



Version-Release number of selected component (if applicable):


How reproducible:

100%

Comment 11 errata-xmlrpc 2022-11-08 10:28:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: kernel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7683