"Antonino A. Daplas" <[email protected]> wrote:
>
> Console writes are done with the console semaphore held. printk will also
> just write to the log buffer and defer the actual console printing
> for later, by the next or current process that will grab the semaphore.
Always by the current process which holds console_sem. Leaving the printing
for the next process would be unacceptably too late for printk.
If printk sees that someone holds console_sem, printk will leave the data
in the log buffer for the current holder of console_sem to print, prior to
that caller releasing console_sem. logbuf_log is used in tricky ways
around console_sem to prevent races in this logic.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]