• Bob Peterson's avatar
    gfs2: Do proper error checking for go_sync family of glops functions · 1c634f94
    Bob Peterson authored
    Before this patch, function do_xmote would try to sync out the glock
    dirty data by calling the appropriate glops function XXX_go_sync()
    but it did not check for a good return code. If the sync was not
    possible due to an io error or whatever, do_xmote would continue on
    and call go_inval and release the glock to other cluster nodes.
    When those nodes go to replay the journal, they may already be holding
    glocks for the journal records that should have been synced, but were
    not due to the ignored error.
    
    This patch introduces proper error code checking to the go_sync
    family of glops functions.
    Signed-off-by: default avatarBob Peterson <rpeterso@redhat.com>
    Reviewed-by: default avatarAndreas Gruenbacher <agruenba@redhat.com>
    1c634f94
glops.c 19.8 KB