mutex_unlock() in interrupt context

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

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

Follow-Ups:
- Re: mutex_unlock() in interrupt context
  - From: Andrew Morton <[email protected]>

References:
- Re: [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3
  - From: Andrew Morton <[email protected]>
- RE: [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3
  - From: "Williams, Dan J" <[email protected]>
- Re: [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: Always zero test in arch/i386/pci/mmconfig-shared.c
Next by Date: Re: Hibernating To Swap Considered Harmful
Previous by thread: Re: [-mm PATCH 0/2] 74% decrease in dispatched writes, stripe-queue take3
Next by thread: Re: mutex_unlock() in interrupt context
Index(es):
- Date
- Thread

[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]