From: Keith Owens <kaos@ocs.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Jim Nelson <james4765@cwazy.co.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Coywolf Qi Hunt <coywolf@gmail.com>,
Jesper Juhl <juhl-lkml@dif.dk>,
David Howells <dhowells@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: printk loglevel policy?
Date: Mon, 03 Jan 2005 14:17:07 +1100 [thread overview]
Message-ID: <28707.1104722227@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 02 Jan 2005 13:41:34 -0800." <41D86A8E.9090400@osdl.org>
On Sun, 02 Jan 2005 13:41:34 -0800,
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>Jim Nelson wrote:
>> Or does printk() do some tracking that I didn't see as to where in the
>> kernel the strings are coming from?
>
>That kind of garbled output has been known to happen, but
>the <console_sem> is supposed to prevent that (along with
>zap_locks() in kernel/printk.c).
Using multiple calls to printk to print a single line has always been
subject to the possibility of interleaving on SMP. We just live with
the risk. Printing a complete line in a single call to printk is
protected by various locks. Print a line in multiple calls is not
protected. If it bothers you that much, build up the line in a local
buffer then call printk once.
next prev parent reply other threads:[~2005-01-03 3:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 2:02 [patch] add loglevel to printk in fs/afs/cmservice.c Jesper Juhl
2004-12-31 2:20 ` printk loglevel policy? Coywolf Qi Hunt
2004-12-31 4:07 ` Jim Nelson
2004-12-31 4:34 ` Jesper Juhl
2005-01-02 14:36 ` Alan Cox
2005-01-02 19:01 ` Jim Nelson
2005-01-02 21:41 ` Randy.Dunlap
2005-01-03 3:17 ` Keith Owens [this message]
2005-01-03 3:52 ` Randy.Dunlap
2005-01-03 4:44 ` Jim Nelson
2005-01-04 10:46 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28707.1104722227@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=coywolf@gmail.com \
--cc=dhowells@redhat.com \
--cc=james4765@cwazy.co.uk \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.