What were you trying to do that didn't work?

On el10 our log anomaly detecting script finds the "Permission denied"
messages in the journal suspicious .

What is the impact of this issue to you?

Little bit annoying

Please provide the package NVR for which the bug is seen:

irqbalance-1.9.4-2.el10.x86_64

How reproducible is this bug?:

always

Steps to reproduce

1. boot
2. wait
3. journalctl -u irqbalanc

Expected results

$ journalctl -u irqbalance
does not contains "Permission denied"  unless the user sets the log level
to more verbose or something unusual really happened.

Actual results

messages like this repeats multiple (>32) times:

Nov 08 05:28:21 hostname irqbalance[80201]: Cannot change IRQ 205 affinity: Permission denied
Nov 08 05:28:21 hostname irqbalance[80201]: IRQ 205 affinity is now unmanaged
Nov 08 05:28:21 hostname irqbalance[80201]: Cannot change IRQ 177 affinity: Permission denied
Nov 08 05:28:21 hostname irqbalance[80201]: IRQ 177 affinity is now unmanaged

The printing likely related to:
https://lore.kernel.org/lkml/20240825131911.107119-1-jeff.xie@linux.dev/T/