Alan Cox writes: > Actually a PS to this while I think about it. spin_locks and mutex type > locks could both do with a macro for > > call_locked(&lock, foo(a,b,c,d))
reiser4 code was publicly humiliated for such macros, but indeed they are useful. The only problem is that one needs two macros: one for foo() returning void and one for all other cases. > > to cut down on all the error path forgot to release a lock type errors. > Nikita.
