Bug 2074317 - genirq/affinity: Consider that CPUs on nodes can be unbalanced
Summary: genirq/affinity: Consider that CPUs on nodes can be unbalanced
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kernel
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ming Lei
QA Contact: ChanghuiZhong
URL:
Whiteboard:
Depends On: 2074315
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-12 00:24 UTC by Ming Lei
Modified: 2022-11-08 11:55 UTC (History)
1 user (show)

Fixed In Version: kernel-4.18.0-391.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2074315
Environment:
Last Closed: 2022-11-08 10:28:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/rhel/src/kernel rhel-8 merge_requests 2591 0 None None None 2022-04-24 02:47:52 UTC
Red Hat Issue Tracker RHELPLAN-118615 0 None None None 2022-04-12 00:31:54 UTC
Red Hat Product Errata RHSA-2022:7683 0 None None None 2022-11-08 10:29:27 UTC

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


Note You need to log in before you can comment on or make changes to this bug.