> For userland<->kernel transactions we have the console_semaphore to
> protect us. It is also used for console_callback. The console_semaphore is
> not used internally to protect global variables :-( To do this properly
> would take quite a bit of work.
It looks like all these globals need a lock -- they can race on SMP or
with kernel preemption.
Is it really going to be that hard to wrap a lock around their access,
because I think this is going to bite SMP users.
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/