> That's easy to solve by (as posted on netdev) making sure all CPUs are
> running a `freeze' thread on module removal. If that's *all* it's
> for, it's both overkill for struct fs, and insufficient for other
> congruent cases.
Make sure you cover the hard real time task that wont be pre-empted case.
Your freeze thread also can deadlock very very easily. Suppose your freeze
thread pre-empts a thread holding a resource that has to be released for the
module unload.
Basically that proposal seems to be a walking priority inversion problem
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 Jun 26 2000 - 21:00:06 EST