ocfs2: don't use handle for locking in allocation functions
authorMark Fasheh <mark.fasheh@oracle.com>
Sat, 7 Oct 2006 01:34:35 +0000 (18:34 -0700)
committerMark Fasheh <mark.fasheh@oracle.com>
Sat, 2 Dec 2006 02:27:49 +0000 (18:27 -0800)
commitda5cbf2f9df922cfdafa39351691fa83517f1e25
tree845dc288b72f0408870f50605bb3c96eec978dd8
parent8d5596c687c49c1d8812c3456946dec15d069139
ocfs2: don't use handle for locking in allocation functions

Instead we record our state on the allocation context structure which all
callers already know about and lifetime correctly. This means the
reservation functions don't need a handle passed in any more, and we can
also take it off the alloc context.

Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
fs/ocfs2/dir.c
fs/ocfs2/file.c
fs/ocfs2/localalloc.c
fs/ocfs2/localalloc.h
fs/ocfs2/namei.c
fs/ocfs2/suballoc.c
fs/ocfs2/suballoc.h