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>

diff --cc fs/ocfs2/dir.c
Simple merge

diff --cc fs/ocfs2/file.c
Simple merge

diff --cc fs/ocfs2/localalloc.c
Simple merge

diff --cc fs/ocfs2/localalloc.h
Simple merge

diff --cc fs/ocfs2/namei.c
Simple merge

diff --cc fs/ocfs2/suballoc.c
Simple merge

diff --cc fs/ocfs2/suballoc.h
Simple merge