Genirq/affinity: Handle affinity setting on inactive interrupts correctly * tag 'irq-urgent-' of git:///pub/scm/linux/kernel/git/tip/tip: Is allocated, which makes the X86 hack go away" Requested affinity setting and then establish it when the interrupt To find all affected drivers, change the core code to store the X86 has a hacky workaround for this, but other This because interrupts are immediately fully initialized atĪllocation time. When interrupts are inactive with the modern hierarchical irqdomainĭesign, the interrupt chips are not necessarily in a state whereĪffinity changes can be handled. Handle affinity setting on inactive interrupts correctly when Of course nobody noticed that the existing users break Initial code was written, but at some point later it was required This used to "work" because the pointer was not stored when the The coreĬode stores a pointer to it which can lead to a use after free or The node after the domain has been created successfully. Make the handling of the firmware node consistent and do not free Merge tag 'irq-urgent-' of git:///pub/scm/linux/kernel/git/tip/tip into master
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |