On Sun, 25 Jun 2000, Andrew Morton wrote:
> It'll work. What's your take on the 'grab all the other CPUs' idea?
> That pushes all the module uglies into one place.
Unfortunately, it doesn't. It creates a huge "schedule() == race" zone and
puts it into a lot of drivers. Basically, if you trust the core code
(smaller and better looked after) less than you trust drivers... And no,
variant with _that_ check in schedule() doesn't look like a good idea.
> <brokenrecord> But I would rather be spending time looking at timer
> deletion races, which are more important than module unload races - they
> have no workaround </brokenrecord>
URL?
-
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 Jun 26 2000 - 21:00:07 EST