Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 946426[details]
output from `strace -e trace=file irqbalance --debug --oneshot`
Description of problem:
If irqbalance doesn't have right to change irq smp affinity it will silliently continue without any warning in logs what so ever.
How reproducible:
Run irqbalance with
Steps to Reproduce:
1. log yourself as regular user
2. set IRQBALANCE_BANNED_CPUS
3. run irqbalancer
4. check /proc/irq/*/smp_affinity if was changed by irqbalance to value coresponding with IRQBALANCE_BANNED_CPUS (if you've done everything right value should stay unchanged due lack of privileges)
5. check irqbalance log (you'll see nothing about failing to set SMP affinity)
Expected results:
I belive I should be able to at least see some warning in logs about failing to set SMP affinity
Additional info:
In attachment I'm sending output from my run of `strace -e trace=file irqbalance --debug --oneshot`
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, 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://rhn.redhat.com/errata/RHBA-2015-1279.html
Created attachment 946426 [details] output from `strace -e trace=file irqbalance --debug --oneshot` Description of problem: If irqbalance doesn't have right to change irq smp affinity it will silliently continue without any warning in logs what so ever. How reproducible: Run irqbalance with Steps to Reproduce: 1. log yourself as regular user 2. set IRQBALANCE_BANNED_CPUS 3. run irqbalancer 4. check /proc/irq/*/smp_affinity if was changed by irqbalance to value coresponding with IRQBALANCE_BANNED_CPUS (if you've done everything right value should stay unchanged due lack of privileges) 5. check irqbalance log (you'll see nothing about failing to set SMP affinity) Expected results: I belive I should be able to at least see some warning in logs about failing to set SMP affinity Additional info: In attachment I'm sending output from my run of `strace -e trace=file irqbalance --debug --oneshot`