> > I think perhaps we need a module_lock that forbids just module load/unload
> > when its held. A reader/writer lock with the unload as the writer and
> > the rest as readers ?
>
> IMO I have a better variant. I'm doing an equivalent of routing for the
> device numbers. I.e. maintain a tree of devno blocks. The lowest layer
You are solving only a tiny fraction of the problem. The block/char device
case is far from the entire problem that solving the module problem seperately
might be a good idea ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:14 EST