All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Cooperstein <jerry.cooperstein@charter.net>
To: linux-kernel@vger.kernel.org
Subject: mutex_unlock() in interrupt context
Date: Fri, 13 Jul 2007 19:14:56 -0500	[thread overview]
Message-ID: <46981580.5000008@charter.net> (raw)
In-Reply-To: <20070713170147.6129fc3b.akpm@linux-foundation.org>

kernel/mutex.c says about mutex_unlock():

  * This function must not be used in interrupt context.

However I have done some simple test cases that show
it works without complaint.  Now I understand that one
shouldn't do this for good reasons.  So is this a
good coding practice rule, but something that
could appear in sloppy or poorly designed code?

Jerry Cooperstein
  Axian, Inc., Software Consulting and Training


  reply	other threads:[~2007-07-14  0:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13 22:35 [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3 Dan Williams
2007-07-13 22:35 ` [-mm PATCH 1/2] raid5: add the stripe_queue object for tracking raid io requests (take2) Dan Williams
2007-07-13 22:35 ` [-mm PATCH 2/2] raid5: use stripe_queues to prioritize the "most deserving" requests (take3) Dan Williams
2007-07-13 22:54 ` [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3 Andrew Morton
2007-07-13 22:57   ` Williams, Dan J
2007-07-13 22:57     ` Williams, Dan J
2007-07-13 23:01     ` Andrew Morton
2007-07-13 23:01       ` Andrew Morton
2007-07-13 23:28       ` Williams, Dan J
2007-07-13 23:28         ` Williams, Dan J
2007-07-14  0:01         ` Andrew Morton
2007-07-14  0:01           ` Andrew Morton
2007-07-14  0:14           ` Jerry Cooperstein [this message]
2007-07-17  7:01             ` mutex_unlock() in interrupt context Andrew Morton

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=46981580.5000008@charter.net \
    --to=jerry.cooperstein@charter.net \
    --cc=linux-kernel@vger.kernel.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.