Re: console_lock too early in printk???

Andrew Morton (andrewm@uow.edu.au)
Sat, 01 Jul 2000 12:45:23 +1000


There's one thing which bugs me about the console code.

console_softint() calls change_console() calls kill_proc().

This means that we're delivering a signal from within a softirq. Looks
like it can call wake_up_process(), kmalloc(), etc, etc. It also checks
the permissions on *current!

Is all this activity legitimate from within a tasklet?

Secondly, this is all done with console_lock held, so if anyone does a
printk() will it not deadlock?

-
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/