Dave G. (or anyone else) - there is something that I've noticed that might be related to this.
If I do a test that requires 'connld' to be loaded, I can't unload 'streams' without 'streams-connld' first getting unloaded. E.g.,
> modprobe streams > <test involving connld> > modprobe -r streams
Doesn't work - it will report the streams module busy. And it is, in a way; streams-connld hasn't been unloaded. When I then do
> modprobe -r streams-connld
Both modules unload OK. I.e., streams-connld doesn't get unloaded by streams (though if both autoload, this problem won't be noticed).
I haven't reviewed the code (that's why I'm posting this; maybe someone else is current on module loading/unloading), but it seems to me that although the base streams module unloads drivers, that doesn't see modules, because modules aren't chrdevs. Something else needs to happen to unload dependent modules, and it's not being done.
Does this make sense?
-John
David Lehmann wrote:
David Grothe wrote:
Since this seems to be pipe related and since John has done some work on pipes/fifos in the mean time, could you run a test with the latest version to see if the problem still exists. If so, I will add it to my list of things to tend to.
Two years ago it was related to a pipe. Today, it is a pushable module pushed on a regular stream with a streams driver at the other end.
_______________________________________________ Linux-streams mailing list [EMAIL PROTECTED] http://gsyc.escet.urjc.es/mailman/listinfo/linux-streams
