[GFS2] Fix lock ordering bug in page fault path
authorSteven Whitehouse <swhiteho@redhat.com>
Fri, 4 Aug 2006 19:41:22 +0000 (15:41 -0400)
committerSteven Whitehouse <swhiteho@redhat.com>
Fri, 4 Aug 2006 19:41:22 +0000 (15:41 -0400)
commit59a1cc6bdabf5ed148b48808ad1a418d87f5e6bf
tree6463071a09201040267702e895d63359e62c393d
parent899bb264507cfed83922bf14cd66a073494601ba
[GFS2] Fix lock ordering bug in page fault path

Mmapped files were able to trigger a lock ordering bug. Private
maps do not need to take the glock so early on. Shared maps do
unfortunately, however we can get around that by adding a flag
into the flags for the struct gfs2_file. This only works because
we are taking an exclusive lock at this point, so we know that
nobody else can be racing with us.

Fixes Red Hat bugzilla: #201196

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
fs/gfs2/incore.h
fs/gfs2/log.c
fs/gfs2/ops_address.c
fs/gfs2/ops_vm.c
fs/gfs2/recovery.c