fixes for unified wine & kernel locking script
commita3887c03b0d6b524285a8d11c7cfc9cc96e6230a
authorDan Carpenter <error27@gmail.com>
Thu, 10 Dec 2009 20:12:08 +0000 (10 22:12 +0200)
committerDan Carpenter <error27@gmail.com>
Thu, 10 Dec 2009 20:12:08 +0000 (10 22:12 +0200)
tree5f0b732b5f3be26073a475a35c00893b85f3e061
parentd83d244eebbdf600d6a214fe0628bf6f3b0230d8
fixes for unified wine & kernel locking script

Handle locks where the RETURN_VAL is locked.  Before we weren't using the
function_assign_hook() so it was totally wrong.

Added a bunch of lock functions with a double underscore on the front and
shifted things around a bit.

Also added a bunch more entries to the table for handling irq disable
and enable.

One thing which is interesting is that depending on the configuration
_spin_lock_irqsave can take either 1 or 2 options.
+  {"_spin_lock_irqsave", LOCK, "irqsave", RETURN_VAL, ret_any},
+  {"_spin_lock_irqsave", LOCK, "irqsave", 1, ret_any},

There are probably still quite a few bugs left.

Signed-off-by: Dan Carpenter <error27@gmail.com>
check_wine_locking.c