> Hmm, I thought the sched stuff all runs under the network brlock? If
> so, it doesn't need to be held in, since it's not preemptible.
> I haven't checked, though...
It runs under semaphore.
Which does not matter at all, because the hole
<an instance is cloned here>
remained in any case, be it under some preemptive, nonprepemtive lock or
not under a lock at all.
BTW, Rusty, a question... I do not understand, what is purpose of this "new"
module stuff at all? If we still need to query something in module.c to create
each instanse of something it smells exactly "old" broken approach. I just
do not see differences. It is not essential in this particular case,
but it would be funny to ask it each time when creating a tcp socket.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/