| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 21 Nov 2014 02:32:44 +0100 (CET) From: Thomas Gleixner <tglx@...utronix.de> To: Suravee Suthikulpanit <suravee.suthikulpanit@....com> cc: jiang.liu@...ux.intel.com, marc.zyngier@....com, linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] irqdomain: Fix NULL pointer dererence in irq_domain_free_irqs_parent On Thu, 20 Nov 2014, suravee.suthikulpanit@....com wrote: > This patch checks if the parent domain is NULL before recursively freeing > irqs in the parent domains. Which is nonsense, because if the thing has not been allocated in the first place, then it cannot explode in the free path magically, except there is a missing check in the allocation path error handling. And that's obviously not the case simply because this originates from: > [<fffffe0000449278>] pci_disable_msix+0x40/0x50 Suravee, this is the last warning. I'm tired of your half baken patches which lack any explanation. Read back on my previous replies to your mails for further explanation. This is not a 'try and error and hack enough nonsensical checks into the code' commercial project. This is core kernel code and requires proper explanation. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists