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

bugzilla at redhat.com bugzilla at redhat.com
Wed Aug 12 04:18:05 UTC 2015


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



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11449 committed in master by Venky Shankar
(vshankar at redhat.com) 
------
commit 7b44b6c16fb538e5f15a255182de4dee781994a0
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

    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: I5ea4d4fc1a91387f7f9d13ca8cb43c88429f02b0
    BUG: 1243391
    Signed-off-by: Raghavendra Bhat <raghavendra at redhat.com>
    Reviewed-on: http://review.gluster.org/11449
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>

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


More information about the Bugs mailing list