summaryrefslogtreecommitdiffstats
path: root/arch/x86/Kbuild
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2020-07-09 11:53:06 +0200
committerThomas Gleixner <tglx@linutronix.de>2020-07-14 17:44:42 +0200
commite3beca48a45b5e0e6e6a4e0124276b8248dcc9bb (patch)
tree65c253af1f9b2531f1129f5223b8e221542183dc /arch/x86/Kbuild
parentLinux 5.8-rc4 (diff)
downloadlinux-e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb.tar.xz
linux-e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb.zip
irqdomain/treewide: Keep firmware node unconditionally allocated
Quite some non OF/ACPI users of irqdomains allocate firmware nodes of type IRQCHIP_FWNODE_NAMED or IRQCHIP_FWNODE_NAMED_ID and free them right after creating the irqdomain. The only purpose of these FW nodes is to convey name information. When this was introduced the core code did not store the pointer to the node in the irqdomain. A recent change stored the firmware node pointer in irqdomain for other reasons and missed to notice that the usage sites which do the alloc_fwnode/create_domain/free_fwnode sequence are broken by this. Storing a dangling pointer is dangerous itself, but in case that the domain is destroyed later on this leads to a double free. Remove the freeing of the firmware node after creating the irqdomain from all affected call sites to cure this. Fixes: 711419e504eb ("irqdomain: Add the missing assignment of domain->fwnode for named fwnode") Reported-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Marc Zyngier <maz@kernel.org> Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/873661qakd.fsf@nanos.tec.linutronix.de
Diffstat (limited to 'arch/x86/Kbuild')
0 files changed, 0 insertions, 0 deletions