kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: neil.baylis@gmail.com (Neil Baylis)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Calling printk with locks held
Date: Thu, 2 Jun 2011 13:43:05 -0700	[thread overview]
Message-ID: <BANLkTim4iXf79fnUswpEDdgZ5rQ7RfOFjA@mail.gmail.com> (raw)

I've just been told that it's not OK to call printk while holding a lock.
This came as a surprise to me, as I've written thousands of lines of code
that calls printk while holding multiple locks, and have not seen any
problem. The only explanation I was given was that it can deadlock.

Is this correct? I thought there were very few places where it was not safe
to call printk.

Neil Baylis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110602/5d2ee90a/attachment.html 

             reply	other threads:[~2011-06-02 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 20:43 Neil Baylis [this message]
2011-06-02 22:45 ` Calling printk with locks held Mulyadi Santosa
2011-06-02 22:54 ` Dave Hylands

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=BANLkTim4iXf79fnUswpEDdgZ5rQ7RfOFjA@mail.gmail.com \
    --to=neil.baylis@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).