From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932341AbbFINRT (ORCPT ); Tue, 9 Jun 2015 09:17:19 -0400 Received: from www.linutronix.de ([62.245.132.108]:46435 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751102AbbFINRL (ORCPT ); Tue, 9 Jun 2015 09:17:11 -0400 Date: Tue, 9 Jun 2015 15:17:15 +0200 (CEST) From: Thomas Gleixner To: Mason cc: LKML , Linux ARM , "Rafael J. Wysocki" Subject: Re: [IRQ] Buggy driver makes __setup_irq segfault In-Reply-To: <5576E457.6020805@free.fr> Message-ID: References: <5576E457.6020805@free.fr> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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