[GFS2] Put back semaphore to avoid umount problem
commit61be084efcc4451934257350281962595418a33c
authorSteven Whitehouse <swhiteho@redhat.com>
Mon, 29 Jan 2007 11:51:45 +0000 (29 11:51 +0000)
committerSteven Whitehouse <swhiteho@redhat.com>
Mon, 5 Feb 2007 18:38:14 +0000 (5 13:38 -0500)
tree3f7b3e0d93f52803f27aa3268a4bd7098e48ae4d
parentbbb28ab7599789740b2233a0805d22aefb97f533
[GFS2] Put back semaphore to avoid umount problem

Dave Teigland fixed this bug a while back, but I managed to mistakenly
remove the semaphore during later development. It is required to avoid
the list of inodes changing during an invalidate_inodes call. I have
made it an rwsem since the read side will be taken frequently during
normal filesystem operation. The write site will only happen during
umount of the file system.

Also the bug only triggers when using the DLM lock manager and only then
under certain conditions as its timing related.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Cc: David Teigland <teigland@redhat.com>
fs/gfs2/glock.c