linux-kernel - Re: [IRQ] Buggy driver makes __setup

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1506091515060.4133@nanos>
Date:	Tue, 9 Jun 2015 15:17:15 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Mason <slash.tmp@...e.fr>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [IRQ] Buggy driver makes __setup_irq segfault

On Tue, 9 Jun 2015, Mason wrote:
> I'm a noob, so I suppose this behavior is expected, but I'm reporting it,
> just in case. (I tested with 3.14.41)
> 
> Consider this buggy driver, calling request_irq() multiple times,
> and not calling free_irq in the cleanup routine.

Not freeing things in the module exit code will make stuff explode,
not only interrupts. So yes, it's expected behaviour.

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/