lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 13 Jul 2007 19:14:56 -0500
From:	Jerry Cooperstein <jerry.cooperstein@...rter.net>
To:	linux-kernel@...r.kernel.org
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ