Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 Oct 2002 12:08:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 Oct 2002 12:08:00 -0400 Received: from chaos.physics.uiowa.edu ([128.255.34.189]:45495 "EHLO chaos.physics.uiowa.edu") by vger.kernel.org with ESMTP id ; Wed, 23 Oct 2002 12:07:54 -0400 Date: Wed, 23 Oct 2002 11:13:58 -0500 (CDT) From: Kai Germaschewski X-X-Sender: kai@chaos.physics.uiowa.edu To: Armin Schindler cc: Linux Kernel Mailinglist Subject: Re: module_init in interrupt context ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1002 Lines: 25 On Wed, 23 Oct 2002, Armin Schindler wrote: > With kernel 2.4.19 I noticed that calls from module_init() > may be done in interrupt context. I didn't have a problem here > before 2.4.17. Well, I am positive that this is not so. > E.g. in module_init() I use pci_module_init() for my driver > (I don't have HOTPLUG enabled), the when the .probe function is called > and the card is detected I create a proc entry for this new > found device, but most of the time create_proc_entry causes > BUG(), because it is called from interrupt context. I think you should provide the backtrace and the code in questions. Obviously, something is wrong, but it's virtually impossible that module_init() runs from irq context, so it has to be something else. --Kai - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/