[Bugs] [Bug 1255351] fail the fops if inode context get fails

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1255351



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11966 committed in release-3.7 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit 3becc47609e04f9bfd482810ef450bd1a8703fd7
Author: Raghavendra Bhat <raghavendra at redhat.com>
Date:   Sat Jun 27 13:17:32 2015 +0530

    features/bit-rot-stub: fail the fop if inode context get fails

                           Backport of http://review.gluster.org/11449

    In stub, for fops like readv, writev etc, if the the object is bad, then
the fop
    is denied. But for checking if the object is bad inode context should be
    checked. Now, if the inode context is not there, then the fop is allowed to
    continue. This patch fixes it and the fop is unwound with an error, if the
inode
    context is not found.

    Change-Id: I0dcbf80889427d4c0404e00bc6c773f6fe8fc8db
    BUG: 1255351
    Signed-off-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/11966
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Kotresh HR <khiremat at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the Docs Contact for the bug.