[Bugs] [Bug 1161886] rename operation leads to core dump

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 29 03:49:36 UTC 2015


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



--- Comment #6 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9420 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit b17122ffc75c65bda2cf3b3d99832bbf2718e8d3
Author: Xavier Hernandez <xhernandez at datalab.es>
Date:   Sat Nov 8 21:46:41 2014 +0100

    ec: Fix posix compliance failures

    This patch solves some problems that caused dispersed volumes to not
    pass posix smoke tests:

    * Problems in open/create with O_WRONLY
        Opening files with -w- permissions using O_WRONLY returned an EACCES
        error because internally O_WRONLY was replaced with O_RDWR.

    * Problems with entrylk on renames.
        When source and destination were the same, ec tried to acquire
        the same entrylk twice, causing a deadlock.

    * Overwrite of a variable when reordering locks.
        On a rename, if the second lock needed to be placed at the beggining
        of the list, the 'lock' variable was overwritten and later its timer
        was cancelled, cancelling the incorrect one.

    * Handle O_TRUNC in open.
        When O_TRUNC was received in an open call, it was blindly propagated
        to child subvolumes. This caused a discrepancy between real file
        size and the size stored into trusted.ec.size xattr. This has been
        solved by removing O_TRUNC from open and later calling ftruncate.

    Change-Id: I20c3d6e1c11be314be86879be54b728e01013798
    BUG: 1161886
    Signed-off-by: Xavier Hernandez <xhernandez at datalab.es>
    Reviewed-on: http://review.gluster.org/9420
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=SUvgs3nTit&a=cc_unsubscribe


More information about the Bugs mailing list