Fix bug in cmirror that caused incorrect status info to print on some nodes.
    
    Here's the upstream commit message:
    
    commit 172a9457bf8dcc1e5c3a607be2e8d1ac80ac619b
    Author: Jonathan Earl Brassow <jbrassow@redhat.com>
    Date:   Thu Apr 26 17:30:49 2012 +0000
    
        Fix bug in cmirror that caused incorrect status info to print on some nodes.
    
        Looking at the code in cmirrord/local.c, we can see the various different
        request types handled in different ways.  Some information that is non-changin
        does not need to go around the cluster and can be short-circuited.  For
        example, once the cluster mirror is in-sync, it is pointless to continue
        sending that query around the cluster.  We can save network bandwidth and repl
        directly back to the kernel.  When it comes to status information, there are
        two types 'TABLE' and 'INFO'.  The 'TABLE' information never changes and
        belongs to the group of requests that can be safely short-circuited.  The
        'STATUS' information can change - and will change if a device fails.  Thus it
        cannot be short-circuited, but this is exactly what was found.  The 'STATUS'
        information request was being short-circuited and therefore never reporting th
        failure condition to anyone other than the "server" that experienced it
        directly.