diff options
author | Bob Peterson <rpeterso@redhat.com> | 2017-07-18 12:36:01 -0500 |
---|---|---|
committer | Bob Peterson <rpeterso@redhat.com> | 2017-08-09 09:36:38 -0500 |
commit | 240c6235dfe4fe46f2fd0f2b3c15b3a22100a75e (patch) | |
tree | d619273688a72fd0a28badeb5912e35a84566a29 /fs/devpts | |
parent | 9c1b28081f43c0f14ccbcad02a6e0f227c072da2 (diff) | |
download | linux-stable-240c6235dfe4fe46f2fd0f2b3c15b3a22100a75e.tar.gz linux-stable-240c6235dfe4fe46f2fd0f2b3c15b3a22100a75e.tar.bz2 linux-stable-240c6235dfe4fe46f2fd0f2b3c15b3a22100a75e.zip |
GFS2: Clear gl_object when deleting an inode in gfs2_delete_inode
This patch adds some calls to clear gl_object in function
gfs2_delete_inode. Since we are deleting the inode, and the glock
typically outlives the inode in core, we must clear gl_object
so subsequent use of the glock (e.g. for a new inode in its place)
will not have the old pointer sitting there. In error cases we
need to tidy up after ourselves. In non-error cases, we need to
clear gl_object before we set the block free in the bitmap so
residules aren't left for potential inode creators.
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com>
Diffstat (limited to 'fs/devpts')
0 files changed, 0 insertions, 0 deletions