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: <5F9B7248-82DA-43F1-8937-8B52D5146298@holtmann.org>
Date:	Fri, 22 Feb 2008 00:30:45 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Simon Richter <sjr@...ian.org>, Tilman Schmidt <tilman@...p.cc>,
	Gregory Nietsky <gregory@...worksentry.co.za>,
	Jeff Garzik <jeff@...zik.org>, kkeil@...e.de,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	isdn4linux@...tserv.isdn4linux.de, Sam Ravnborg <sam@...nborg.org>
Subject: Re: Plans for mISDN? Was: [PATCH 00/14] [ISDN] ...

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@...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

Powered by Openwall GNU/*/Linux Powered by OpenVZ