| commit | 300c7d75f3a5e8edd3e390ccd56b808f3fb14e33 | |
| author | Steven Whitehouse <swhiteho@redhat.com> | |
| Mon, 27 Nov 2006 14:55:28 +0000 (27 09:55 -0500) | ||
| committer | Steven Whitehouse <swhiteho@redhat.com> | |
| Thu, 30 Nov 2006 15:36:53 +0000 (30 10:36 -0500) | ||
| tree | 1cc627b0e6ef37c3e72691cc75c5be5db14cac72 | treesnapshot (tar.gz zip) |
| parent | cb4c03131836a55bf95e1c165409244ac6b4f39f | commitdiff |
[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>
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>
| fs/gfs2/ops_inode.c | diffblobblamehistory |