Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932931AbYBUXbJ (ORCPT ); Thu, 21 Feb 2008 18:31:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756021AbYBUXax (ORCPT ); Thu, 21 Feb 2008 18:30:53 -0500 Received: from senator.holtmann.net ([87.106.208.187]:59705 "EHLO mail.holtmann.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755713AbYBUXaw (ORCPT ); Thu, 21 Feb 2008 18:30:52 -0500 Cc: Simon Richter , Tilman Schmidt , Gregory Nietsky , Jeff Garzik , kkeil@suse.de, Greg KH , linux-kernel@vger.kernel.org, isdn4linux@listserv.isdn4linux.de, Sam Ravnborg Message-Id: <5F9B7248-82DA-43F1-8937-8B52D5146298@holtmann.org> From: Marcel Holtmann To: Andi Kleen In-Reply-To: <47BE06EB.6010301@firstfloor.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ... Date: Fri, 22 Feb 2008 00:30:45 +0100 References: <098123kjff90231nv098233rnvd908u234@garzik.org> <20080217195235.GN14588@uranus.ravnborg.org> <20080218045209.GA15141@kroah.com> <20080219085033.GA1775@uranus.ravnborg.org> <47BAA072.9050601@networksentry.co.za> <47BC370F.3000705@imap.cc> <47BD5360.5070706@debian.org> <47BE06EB.6010301@firstfloor.org> X-Mailer: Apple Mail (2.919.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1198 Lines: 32 Hi Andi, >> that is not a big problem at all. If you have to enforce a specific >> module load order then create some dummy exports like misdn_load() >> and >> use them from the module that depends on it. > > That's not necessarily enough. There are races during module load > when the next module is loaded already before the module it depends > on has finished initializing. we were talking about the load order. This will solve the load order, but if we have races like the kind you described, then the whole mISDN design is broken. So if that is the fact, then my understanding is that we have too many modules. Simple combine the modules and use proper locking. More modules is not always better. > I regularly run into such a problem on my workstation with one > of the USB serial drivers for example. It errors out when autoloaded > during boot, but loads fine on retry later. Report this to the USB mailing list. Regards Marcel -- 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/