summaryrefslogtreecommitdiff
path: root/lib/locking-selftest.c
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2006-11-27 09:55:28 -0500
committerSteven Whitehouse <swhiteho@redhat.com>2006-11-30 10:36:53 -0500
commit300c7d75f3a5e8edd3e390ccd56b808f3fb14e33 (patch)
tree1cc627b0e6ef37c3e72691cc75c5be5db14cac72 /lib/locking-selftest.c
parentcb4c03131836a55bf95e1c165409244ac6b4f39f (diff)
[GFS2] Fix recursive locking in gfs2_permission
Since gfs2_permission may be called either from the VFS (in which case we need to obtain a shared glock) or from GFS2 (in which case we already have a glock) we need to test to see whether or not a lock is required. The original test was buggy due to a potential race. This one should be safe. This fixes Red Hat bugzilla #217129 Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Diffstat (limited to 'lib/locking-selftest.c')
0 files changed, 0 insertions, 0 deletions